=== rickspencer3-afk is now known as rickspencer3 === rickspencer3 is now known as rickspencer3-afk === Nafallo_ is now known as Nafallo [10:45] hi, I've a question about using NotifyOSD with pynotify: which hints are supported for Notification objects? [10:45] especially: should setting the "x" and "y" hint work? [10:46] and yes, I would like to change the position of a bubble [10:47] thekorn: no they are not, and are unlikely to be supported in the future [10:47] thekorn: you can't change it ;) [10:47] ok, so you do not intend to completly implement the notification spec ?! [10:48] I think it's more or less the idea (im speaking as an user though) [10:48] Because having notifications on every part of the screen just sucks :) [10:49] and why is it not reflected in pynotify.get_server_caps()? [10:49] that's a more interesting concern [10:49] you might want to ask MacSlow. [10:49] thekorn: the spec says supporting those hints is not mandatory [10:49] but if its not supported it should be in get_server_caps [10:50] thekorn, grab notify-osd trunk and check out th python-examples in notify-osd/examples/*.py [10:50] agateau, ok, good point [10:50] * SiDi waves at MacSlow. [10:50] thekorn, that's got everything you need to properly test for supported caps [10:50] ola SiDi [10:51] thekorn, it's ready to cut&paste code, so you should be able to get on with you work quickly [10:51] there's no specified cap for this [10:52] it would be possible to add an x-canonical- capability [10:52] thekorn, notify-osd takes the liberty to ignore the (optional) x/y-hints [10:52] MacSlow, ok, so my question is: why is there no "does not support x,y hint" capability [10:52] but adding a capability to only not set it would be odd [10:52] http://www.galago-project.org/specs/notification/0.9/x408.html [10:52] thekorn: this needs to be added to the Galago spec [10:52] * agateau notes this [10:53] thekorn, because that feature causes overlapping notifications [10:53] MacSlow: i think thekorn means he would like to test whether we support it or not [10:53] but galago spec does not provide a cap we could set to false atm [10:53] wow, this is complex [10:54] indeed, right now it's only spit out as a remark that x/y-hints are not supported in the examples [10:55] thekorn: you may also want to have a look at this one: http://bazaar.launchpad.net/~agateau/notify-osd/take2/annotate/head%3A/tests/notifyosd.py [10:55] for inspiration [10:58] ok, thanks everbody, maybe I have to review my usage of notifyosd, that's what I have so far http://dl.getdropbox.com/u/174479/recordmydesktop_visualizer.ogv [10:58] but maybe I have to use my own window for this [10:59] thekorn, gee... is that just for "messing around" or do you want to really develop that into something serious? [10:59] thekorn, I feel that you might be "abusing" notifications there a bit :) [11:00] MacSlow, I've never done any serious things, so it is just for messing around ;) [11:00] phew ok :) [11:00] fun anyway [11:00] for sure [11:01] and yes, it is abusing of the notification system [11:01] thekorn, I guess you wanted the bubble to appear at the text-cursor position then or something, right? ;) [11:01] MacSlow, no just in the region of the screen which is recorded === DrPepperKid is now known as MacSlow [12:43] * MacSlow -> lunch === rickspencer3-afk is now known as rickspencer3 === YpsyZNC is now known as Ypsy === rickspencer3 is now known as rickspencer3-afk === Ypsy is now known as YpsyZNC === rickspencer3-afk is now known as rickspencer3