I can certainly try, I am moderately advanced programmer, though usually just on my own projects, I'm not so used to reading/working with other people's code. Do you have any suggestions on where to look in the code? I suppose I can start by adding a log call for the position, and go from there, but if you (or anyone else) had any other suggestions or guesses, that'd be great.
Also, just a further note (more so that I remember myself that I tested this when I get back from class tonight): If I post a message on the integrated card, open Grapher (to switch to discrete), and then kill grapher (to switch back to integrated), the next growl message overlaps, even though both were posted from the integrated card. So, it isn't necessarily even that the position is being stored on the vid card (since switching away and back, without any postings in between, still overlaps), but somehow the change of card blows away the positioning information. (As far as I know, the integrated card is always on, so I do not think switching away would clear out its RAM, unlike the discrete card which is powered down when not in use). Likewise, posting with Grapher open (discrete), killing grapher (switch to integrated), and re-opening Grapher (back to discrete), and posting again, it overlaps. Anyway, thanks for responding. At least now I know that I need to do more testing. I just assumed someone else would have a multi-GPU computer. Now that I know you need someone to hunt it down, I'll get on it. On May 9, 2011, at 10:52 AM, Peter Hosey wrote: > On May 9, 2011, at 10:41:41, Dylan wrote: >> This is a really annoying bug, and I'd really like to help track it down. >> Anyone else have this problem? I really dislike bumping my own thread, but >> since no one has responded, I am not even 100% sure that this is getting >> sent to the group properly! > > It is. > > Somebody else reported it in another thread, but since (as far as we know) it > only happens on multiple-GPU machines, there's nothing we can do to debug it. > I can't even guess how it's possible, since Growl does not store its > knowledge of the notification windows and their locations on the GPU. > > There are only two ways this will get fixed: > > - Somebody with a multiple-GPU Mac and programmer-fu (possibly you?) does all > the debugging themselves and submits a patch. > - One of us acquires a multiple-GPU Mac. > > -- > You received this message because you are subscribed to the Google Groups > "Growl Discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/growldiscuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
