On 04/17/2010 08:50 PM, Christopher Michael wrote: > On 04/17/2010 08:46 PM, daniele_athome wrote: >> On Sun, Apr 18, 2010 at 02:28, Christopher Michael >> <cpmicha...@comcast.net> wrote: >>> Identical to e17 zones in reality. I just used "illume zones" so that >>> outside apps (like elementary apps) would have access to the individual >>> zones. >>> >> >> Ehm sorry don't know what are e17 zones neither :-) >> The best explanation I have found so far is here (courtesy of xcomp) :
http://xcomputerman.com/pages/archives/2005/01/04/in-the-zone/ dh >>> /* set this window to not accept or take focus */ >>> ecore_x_icccm_hints_set(window->evas_win, 0, 0, 0, 0, 0, 0, 0); >>> >>> on your home window(s) and they will be ignored by the focus stack. >>> >> >> I just did it, but seems that the problem is not related to the home >> screen. >> I have my app taking building those two windows; the first gets >> activated through a dbus call >> (evas_object_show/elm_win_activate/evas_object_focus_set). The second >> window is activated by the first one. >> When I (the user) close the second window, the first doesn't get the >> focus (the screen shows the E17 background window). >> > Is your second window a 'child' of the first ? (ie: transient_set) ?? > Could be an odd problem there wrt refocus of the parent (tho I have yet > to encounter a case where it fails through). > > dh > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
