Nathan Ingersoll wrote: > On 3/18/07, Kim Woelders <[EMAIL PROTECTED]> wrote: >> Clients that bother about allowed actions (typically a taskbar) should >> monitor the property and keep a local allowed actions state and not >> query the server using e.g. ecore_x_netwm_allowed_action_isset every >> time it needs the info. > > Does it make sense to keep the function for the case of the window > manager restarting or starting up with existing client windows? > Not in my opinion. Seen from the WM the allowed actions list is an output only thing which e.g. taskbars can monitor to see which actions the WM provides for a particular client window. It makes no sense to fetch these on startup as the WM in its nature is completely in charge anyway of which actions it will perform on a window.
Even if the WM should pick up old values or ones set by a client the way to go would not be to pick them off one by one using ecore_x_netwm_allowed_action_isset but to fetch all of them in one go using ecore_x_netwm_allowed_action_get. /Kim ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
