Since the people developing these updates seem to be regularly making magic, I've got two questions:
Would it be possible to change the direction long-touch menus open from the point of touch?
Also, how about moving the status bar from the top to the bottom?

Having options for both would really improve the touch-friendliness of the UI, which seems to be suffering from some decisions made with the stylus in mind.

Specifically, menus in maemo 5 prefer to open downwards from the top, or down and to the right. That means you've got to move your thumb to actually see the menu, and in many apps lifting your thumb off the screen leads to the menu closing.
The statusbar location is not bad, really, but with the keyboard open, being able to switch apps and browse menus could be easier with the bar on the bottom of the screen.

Maybe not everyone would need it, but more options is always better, no?

Well ****,
Apparently the commit khertan reversed didn't fix the bug :/, earlier post deleted. BUT the issue is isolated to raster.
(Run any app with -graphicssystem native and you'll see the bug gone)

Sad to hear that delay. I thought i was actually successfull at testing Metro app.

Enabling WSEGL_UseHWSync is unstable - if you want it on your device, enable it and be done. It will remain through any and all CSSU updates. Stop requesting it as it is NOT fit for all devices.

Indeed. With HWSync on, my device randomly freezes and requires a hold-power-button exit. Worst part is that every damn time it happens something goes kablooey in the root.

Most times it goes to that nasty "All telephony functions" error and need to be booted with keyboard open, and Kernel-power be re-selected to work again (This is repeatable with 80+%, though the reason or details escape me. Why does the filesystem suffer if the phone was shut down? Why the kernel? Why always that part that is fixed by re-selecting the multiboot option - any multiboot option?)

Every now and they it needs to be reverted via BackupMenu.

The crashes are rare (one a week-ish), and 4 out of 5 it lives again via re-selecting the menu in MultiBoot. That makes one BackupMenu restore every other month or so. Not a comfortable thing, but not a disaster, either.

Makes transitions way smoother. Initially didn't see the difference, but once I figured it was why it crashed, turned it off. Now if feels like it's in safe mode or something. I cannot believe I stand on a HW accelerated device packing 1 GHz of heat and it has less of a punch than my old 200 MHz, software emulated phone.

I'm kind of thinking about it. I'd really like it fixed, but I guess other stuff would be nice, too.

Oh, and it makes portrait apps better, too. Microb is bearable in portrait, helps scrolling portrait lists. I'm REALLY thinking about it.

FYI, the crashes only happen when radius and radius_more are set to 0, I haven't noticed anything if they're over 0 (but then again, transitions take a bit more time in that case).

@ndi
My device did not have the problem. I'm using stock kernel and all seems sweet.

Everyone has a different experience with this feature.

Some devices are unstable and some are perfectly fine.

Similar to how some can overclock to 1150Mhz on XLV and be stable. Whereas others can only get to 1000Mhz on Ideal. The weirdness of computers and hardware :P

Here I was thinking that was chucked out the window with that (rather premature) dependency on camera-ui2...

But the camera-ui2 isnt a feature..

Its an open source replacement of a closed component meaning that the CSSU can bug fix and also improve on the original problems with the closed camera component.

Also the whole point of the CSSU being in testing phase is that things won't always be stabled.

Mentalist was talking about options for features.

For example, being able to choose whether you want the default sized task switched or the larger 2 columns or even the single columns mode.