On Sat, Feb 6, 2010 at 6:16 PM, Vincent Torri <vto...@univ-evry.fr> wrote: > > > On Sat, 6 Feb 2010, Brian Wang wrote: > >> On Sat, Feb 6, 2010 at 3:39 PM, Carsten Haitzler <ras...@rasterman.com> >> wrote: >>> >>> On Sat, 6 Feb 2010 15:05:46 +0800 Brian Wang <brian.wang.0...@gmail.com> >>> said: >>> >>>> On Sat, Feb 6, 2010 at 9:39 AM, Carsten Haitzler <ras...@rasterman.com> >>>> wrote: >>>>> >>>>> On Sat, 6 Feb 2010 09:02:34 +0800 Brian Wang >>>>> <brian.wang.0...@gmail.com> >>>>> said: >>>>> >>>>>> On Fri, Feb 5, 2010 at 5:31 PM, Brian Wang <brian.wang.0...@gmail.com> >>>>>> wrote: >>>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> I'm experimenting the cool quicklaunch framework of Elementary to >>>>>>> improve my app startup time. >>>>>>> >>>>>>> I wrote some app to test with it. When it is launched by symlinked >>>>>>> elementary_run, the elementary_quicklaunch outputs lots of: >>>>>> >>>>>> I just svn up and tested the official elementary_testql (symlink'd to >>>>>> elementary_run). Same result. Connection to elementary_quicklaunch >>>>>> generates SPANK errors. The first connection, even with the SPANK >>>>>> errors, brings up the test app, which responds to mouse events. >>>>>> However, subsequent connections to elementary_quicklaunch bring up the >>>>>> same test app windows but they don't respond to mouse events. >>>>>> >>>>>> Is it just me? Any advice to resolve the problem? >>>>> >>>>> happens here too. something has broken. needs looking into. >>>> >>>> OK. I would volunteer to do the digging. However, I'm afraid I don't >>>> have the skill/knowledge to investigate further... Any pointers? >>> >>> something involved in shutting down some subsyetem then later restarting >>> it is >>> losing u the events and getting the complaints. the question is which >>> one(s) >>> abnd why. quicklaunch is failr isolated (its in elm_main.c - theres a 2 >>> stage >>> init and quicklauncher runs 1st stage and then waits for commands - when >>> it >>> gets commands it dlopens the .so for that app then the 2nd stage is run >>> and elm >>> app main is continued with. elementary_run then shuts down everything (x >>> connection and more) re-inits them again and sits and waits) >> >> Thanks for the info. >> >> I did some more digging and tests. The attached patch should >> hopefully fix the problem. (Yes, I did attach the patch. If it's not >> there, please let me know.) >> Please let me know if it's the right fix. :-) > > fixed in svn, thanks
Cool! Now, I can play with elementary_quicklaunch on my target with more confidence. :-) > > Vncent -- brian ------------------ Cool-Karaoke - The smallest recording studio, in your palm, open-sourced http://cool-idea.com.tw/ iMaGiNaTiOn iS mOrE iMpOrTaNt tHaN kNoWlEdGe ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
