[openbox] Startup notification.

[Andrej N. Gritsenko]

    Hello!

Dana Jansens has written on Thursday, 11 July, at 15:28:
>On Thu, Jul 11, 2013 at 2:20 PM, Andrej N. Gritsenko <andrej at rep.kiev.ua>wrote:
>> Dana Jansens has written on Thursday, 11 July, at  8:35:

>> >Some apps don't support this, but then the cursor should stay in a "busy"
>> >state until it times out, rather than staying as an arrow.

>>     May it be that support is broken in official latest release tarball
>> (3.5.0 it is) and fixed only in GIT sources? Because I'm using package in

>Not AFAIK.

>> Also my current Openbox binary shows me:

>> andrej:~> readelf -s /usr/bin/openbox|grep sn_launcher_context_new
>>     42: 00000000     0 FUNC    GLOBAL DEFAULT  UND sn_launcher_context_new

>> which means libstartup_notification is in use by openbox executable.

>It could be a matter of cursor libraries, as the openbox busy cursor is the
>"pointer with stopwatch" kind of cursor, not the "busy waiting" cursor.
>Otherwise, I'm not sure I guess. Running xterm with startupnotification
>enabled should leave an environment variable in the application that would
>prove openbox is doing *something*.

    It seems it does *something*, I've got this in environment for my test
command:

DESKTOP_STARTUP_ID='openbox/sh/24554-6-rep_TIME2191843891'

I would like to understand which cursor libraries should be fixed if that
is really matter.

>Unfortunately we don't have debug logging in the startup notify code..

    It is a pity. Such things should have some debug. :)

    Cheers!
    Andriy.