Carsten Haitzler (The Rasterman) wrote: > On Mon, 31 May 2010 20:21:50 -0400 Christopher Michael > <cpmicha...@comcast.net> > said: > >> On 05/31/2010 08:18 PM, Carsten Haitzler (The Rasterman) wrote: >>> On Mon, 31 May 2010 20:04:05 -0400 Christopher >>> Michael<cpmicha...@comcast.net> said: >>> >>>> Going to start working on adding the Add/Del buttons to the ACPI >>>> Bindings dialog tomorrow and was wondering if anyone had thoughts on how >>>> the Add should work ? >>>> >>>> Should we display a dialog with the list of available ACPI events ? Or >>>> do we want to use an approach like Key bindings dialog where an input >>>> window is presented, and the user triggers the ACPI event they are >>>> interested in ? >>> i would go for "like keybindings" - this would be the right way >> Sounds good :) >> >> ... except there >>> may be niggles with acpid doing things like shutting down your box when u >>> press power to just begin to set it up... then again you need to fix this >>> anyway and get acpid to stop running the scritps that did this to start >>> with. so probably good you find out there and then. :) >>> >> And by "You" I assume you mean "The User" ?? (and not 'me' as in coder >> having to work around this) > > yes - the user. as such there is nothing you can do in code (unless you > literally fuck up peoples os's and packages and blindly delete files and screw > with the acpi config/package and thats just anti-social). as i know there is > no > standard generic way to register yourself as a power manager so the acpi > scripts/setups/whatever do not shut down, suspend, etc. etc. and leave it to > you to do - the user has to modify their distro themselves. right now this is > FAQ material. eventually we need to push for distros to adopt some generic > solution (their power management scripts read some global config > file/dir/whatever and e can insert itself as "hey i manage power stuff so just > let things be" ... or... much better - turn it into a proper system power > management daemon (dbus let's say) and apps like e register they want to > handle > power management (and on disconnect from dbus the power management daemon can > go back to default handling - eg in case no wm is runing or x fails to launch > then at least power button works). but thats long-term and mostly out of our > hands and in those of the distros. the quick fix right now is for people - per > distro, to figure out how their distro handles the "if gnome, kde, etc. is > running - do nothing and let them handle power management" and insert > enlightenment into that list too. thats the quick solution for now. >
In latest Ubuntu(s) this is so. udev registers all acpi keys/events so if you don't have gnome-power-manager running nothing happens. /etc/acpi is almost empty. Sebastian ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
