We are aware of this issue, and are working to find the best solution, so that users with multi user environment have as seamless experience as possible. The new method for talking to Growl, and our method going forward is GNTP, which was designed as a (mainly) single port protocol, and once the first user's Growl latches onto that port, the other user's growl cant get it. Regardless of what we do in the core Growl.app though, ultimately it will also take updates to the framework, as even if we cut off Growl's sockets on the first user, apps from the first user could conceivably than talk to Growl on the second user's account. As another option, we could use a different port for each user, but again, the framework would need updating to support figuring out which port that user's Growl had registered on, and that second user would be frustrated that none of his apps which didn't have the updated framework would work properly (they would still be talking to user 1).
This has been filed as http://code.google.com/p/growl/issues/detail?id=426, and any further updates on its progress will be there. On Jan 27, 4:49 am, Maciej Tarmas <[email protected]> wrote: > Now if I log out from the first account, the second instance of Growl > seems to take over handling the notifications correctly, but as soon > as the first user (the one that has logged in first, than logged out) > logs back in, everything returns to the point where we started. -- 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.
