Hi Mirco,
first of all thanks for your great work on the notify system, I'm following you
blog since some time ago and I really appreciate it!
About this behavior, anyway, I can't understand the underlying logic.
I was here to report it as a bug too, so I wonder if we're iterating the case
with
Andy, that's the currently intended behavior of notify-osd. This is the
fixed slot allocation-scheme introduced with notify-osd 0.9.21.
Synchronous bubles (e.g. volume, brightness) always go in the top slot
and asynchronous ones (e.g. IM-, or email-notifications) always go in
the bottom slot.
**
This picture shows an example from xchat notification, there was nothing
on screen before this appeared. I have also see some of the wireless
notifications use this same slot when the top was empty.
** Attachment added: p1030978-small.jpg
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/31782142/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/31782143/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/31782144/Dependencies.txt
**
Here is a picture when I next pressed volume, note it is able to use the
slot. A subsequent xchat message is still unable to.
** Attachment added: p1030981-small.jpg
http://launchpadlibrarian.net/31782239/p1030981-small.jpg
--
OSD seems to be using the wrong vertical slot for some popups
