On 3/22/2013 10:08, Ken Thomases wrote:
On Mar 21, 2013, at 3:41 PM, C.W. Betts wrote:
On Mar 18, 2013, at 3:22 PM, Ken Thomases <k...@codeweavers.com> wrote:
On Mar 18, 2013, at 4:04 PM, Charles Davis wrote:
At this point, though, I'm wondering if it wouldn't just be easier to have
Explorer draw the balloons itself à la Windows XP.
Probably. I also considered using an NSPopover anchored to the status item.
Again, that's 10.7+ functionality.
We could implement it and do compile- and runtime checks to make sure that the
functions aren't called in unsupported OS X versions. However, this would
probably add fragmentation, and I doubt Alexandre would be happy with this.
I think he'd be OK with some variant of this. He might not want two
implementations, one using NSPopover on 10.7+ and another for 10.6. I don't
know how he'd feel about notification balloons only being implemented on 10.7+.
Although I'm not sure how important notification balloons are in the grand
scheme of things, anyway. I guess users will let us know if they miss them
(unless somebody is inspired to take on that particular corner of unimplemented
functionality beforehand).
I might be wrong but I think it was some .net installer that wanted user
to click on this balloon popup to complete, on the end of installation
process it was just waiting for such user input.
Cheers,
Ken
