2009/11/7 Carsten Haitzler <ras...@rasterman.com>: > On Sat, 7 Nov 2009 08:33:35 +0000 Neil Jerram <neiljer...@googlemail.com> > said: > >> 2009/11/7 Carsten Haitzler <ras...@rasterman.com>: >> > >> > no. the proper way is to set properties on your window. >> >> How exactly does that (setting a property) happen though? Is it > > how does setting the title? or the min/max size of the window happen? the name > and class, window role, if its a dialog, transient for which window, if the > app > would like it to be borderless... all of these are properties. try "xprop" and > clikc on a window. any window (freerunner or desktop - doesn't matter). THOSE > are properties. you can add/create/define any properties you like. they hang > onto the window until they are modified or deleted or the window is deleted. > >> something that the app would normally do in its own startup code? (I > > yes. see above. apps are doing it all the time. it's about the most standard > way to provide information about your window, from title to minimum and > maximum > size to aspect ratios and more. rotation preferences are just yet more > properties like this. if its a "property" of the window - put it as a property > of the window. use the mechanism created for precisely this kind of thing. > dbus > is not that mechanism.
Thanks. I think I'll look at adding this into the e17 WM. If you can recommend a good place in the code to starting working on this (i.e. checking for a rotation property, and invoking xrandr or omnewrotate accordingly), that would be great. Regards, Neil _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community