Re: [Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2013-12-24 Thread Vanessa Lee
Thanks for the patch, though I think eventually this issue needs to be worked out and agreed upon. -Vanessa On Tue, 2013-12-24 at 04:44 +, Heather Van Wilde wrote: > @vanessax Buried in the comments is a patch that is supposed to restore > full functionality. But that, for one, doesn't addr

Re: [Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2014-01-02 Thread Vanessa Lee
I was not out to program anything the day I found out about this problem. I was writing a shell script just to get something displayed on screen after a key press. I found out about notify-osd and used it, it took 5 seconds for me to figure out how to use it. Then I realized that notifications we

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2015-03-18 Thread Vanessa Lee
Matthew Paul Thomas (mpt) we don't know how many people are annoyed with this bug vs those who are not because today, we simply don't have as many competent programmers as we did a decade ago (before the tech industry boom) that will delve this deep into a problem amoung the programming community.

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2015-03-28 Thread Vanessa Lee
I don't quite understand either, and I try to be as inclusive as possible in life, but my complaint is that there is an "official" stance to ignore the requests for a warning on the "official" documentation that says something works that does not. That is inhernetly saying, "yes I officially said

[Bug 1263671] [NEW] gconftool-2 does not accept negative values with --set

2013-12-23 Thread Vanessa Lee
Public bug reported: # gconftool-2 -t int -s /app/myvalue -3 Error while parsing options: Unknown option -3. Run 'gconftool-2 --help' to see a full list of available command line options. ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: New ** Tags: gconftool negative set

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2013-12-23 Thread Vanessa Lee
Having spent 5 minutes learning about notify-osd and then 6 hours trying to figure out what the problem was and finally coming across this, it's appearent there is a dichotomous debate over this timeout issue. I'm not sure if it's already mentioned before, but isn't there a way for the user to set

[Bug 1205660] Re: Users cannot dispel notifications if they are disrupting work

2013-12-23 Thread Vanessa Lee
Allowing an option for the user to specify on the server side, such as click to close, would seem like a good option to me. (yes, I am aware of the fact that notifications are inherently not interactive) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 1176365] Re: Support for ADHD accessibility

2013-12-23 Thread Vanessa Lee
I think this is related to an issue with intentionally ignoring the timeout argument, there is a long discussion about the issue/bug #390508 here: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508 -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 507832] Re: notifications never cleared when new ones keep comming

2013-12-23 Thread Vanessa Lee
I think this problem is either related to or compounded by another issue about timeouts that is unresolved, there is a long standing bug #390508 discussed here: https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/390508 -- You received this bug notification because you are a member of Ubun

[Bug 497703] Re: NotifyOSD slow with repetitive notifications

2013-12-23 Thread Vanessa Lee
I think this problem is either related to or compounded by another issue about timeouts that is unresolved, there is a long standing bug #390508 discussed here: https://bugs.launchpad.net/ubuntu/+source/notify- osd/+bug/390508 -- You received this bug notification because you are a member of Ubun

[Bug 723980] Re: default display time is way too long and non configurable

2013-12-23 Thread Vanessa Lee
They don't seem to want to change the timeout or make it configurable, here is the full discussion about that https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2015-02-02 Thread Vanessa Lee
Yeah I know, I still see the OSD staying on and wondered, oh if there were just some way to make it disappear faster if it wasn't important. Hey, there must be a timeout option... oh wait, I'm not going to fall for that one again. We can waste our time on more productive issues that plaque the wo

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2015-02-06 Thread Vanessa Lee
It would be great if they would accept that, but this is an issue they "won't fix". If they did accept your manual page fix, someone down the line would say, "hey, wouldn't it be great if we could add a timeout option?" Then the cycle of madness repeats (with a longer circumferance). -- You rec

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2014-03-10 Thread Vanessa Lee
Well let's approach this logically, scientifically, sensibly, and reasonably. We have an easy opportunity to add a "choice", to have the option or not. But we are choosing not to have a choice. The whole point of Ubuntu and free software is to be better than commercial, to actually have the best

[Bug 390508] Re: notifyOSD ignores the expire timeout parameter

2014-03-12 Thread Vanessa Lee
Where is the illogical reasoning where: A group of people encountered a timeout option that was not working, spent many hours of their time, lives, and energy, to figure out what was causing it, and only to find out it does nothing but did not warm them of so? They posted about this, and have ask