[maemo-developers] [maemo-developers] running af at 24-bit depth
From: Tommi Komulainen tommi.komulainen at nokia.comDate: Wed Jun 1 19:26:22 EEST 2005
- Previous message: [maemo-developers] running af at 24-bit depth
- Next message: [maemo-developers] running af at 24-bit depth
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2005-05-30 at 16:00 +0300, ext Timo Savola wrote: > On Mon, 2005-05-30 at 15:15 +0300, Aleksandr Koltsoff wrote: > > > The component that provides images to applications (sapwood-server), has a > > hardcoded value in it that is set to 16. Since the process runs without a > > Gdk-context, it's not easy to detect the depth directly (I'm guessing here > > though). > > > > I've modified the server so that the depth can be controlled via an > > environmental variable called SAPWOOD_DEPTH and if it's set to 24, then > > sapwood will use that. > > Let the arms race begin... > > Here's another quick+dirty hack. It gets the depth from the X display > so you don't have to specify it manually. I've included the patch. Thanks for the effort but both are rather ugly hacks. sapwood-server already has an X connection so it could just use GDK to query the depth of the root window. Of course this is not an issue on the target device and I *thought* we managed to bury this issue by introducing Xephyr (I'm running in 16bit so I didn't initially notice it either.) It's a pretty straightforward fix, I'm just not sure when I get around to fix that as it's not exactly critical :-/ You might want to use Xephyr anyway as it has nice redrawing debugging support; just killall -USR1 Xephyr and you'll see which regions are being redrawn. -- Tommi Komulainen <tommi.komulainen at nokia.com>
- Previous message: [maemo-developers] running af at 24-bit depth
- Next message: [maemo-developers] running af at 24-bit depth
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]