Open GoogleCodeExporter opened 8 years ago
The first option, simply cutting growl off for the inactive user is fairly
simple to implement comparatively. However, as someone who doesn't really face
the issue, I can't really comment on what I would prefer to see more.
Original comment by dan...@growl.info
on 27 Jan 2012 at 3:43
Original comment by dan...@growl.info
on 6 Feb 2012 at 4:54
I am using Growl this way :
- a "iTunes" user is always running on my mac in order to keep running iTunes
and EyeTV running
- "human" users are logging on their own sessions when needed, by using the
fast user switching capability - "iTunes" session tools are then still running
in the hidden session
Growl is used on the "iTunes" session to monitor the different actions running
and Prowl allows me to follow that on my iPhone. I decided not to use Growl in
the other sessions as I do not want users being disturbed by "iTunes" session
messages.
Cutting growl off for the "iTunes" user when it is not the main one will not
allow anymore this (or this should be an option).
My vote is :
- having the user's Growl not overlapping but running by default
- having an option that allows to broadcast from a user's Growl to another, on
a per application and per priority base.
Original comment by bip.phil...@gmail.com
on 8 Feb 2012 at 8:25
Original comment by ch...@growl.info
on 18 Jul 2012 at 5:16
Original comment by ch...@growl.info
on 5 Oct 2012 at 4:39
Hello!
I use my Mac with two different users, one for home tasks and one for work.
This is good, because I have different preferences in work as at home.
The desired behaviour as I think is that every user would run a Growl server,
which would display the notifications it receives. Applications could send the
notification either "the simple way" (the same user's Growl would receive it as
the tasks owner) or "broadcasted way" (every user would get it on the same
computer). The user should be able to set this setting per-notification basis.
For example this way I would need only one HardwareGrowler running which can
broadcast events to all users (since events do not differ on the two users).
Another usecase is, when you want to get notified when something happens on the
other user's account (for example he gets an email or the encoder finishes
encoding).
If it is complicated to implement this way, then at least please just enable
users to use two instances of Growl and have one user's applications to be able
to connect only to the local user's Growl server.
The current way, when the 2nd user's growl messages can be not seen is
definetly wrong in every way.
Original comment by gruber.k...@gmail.com
on 4 Dec 2012 at 6:51
Much like user bip_phil, I always have an account running in the background for
my home automation system. I would like to be able to see Growl alerts ("Hey,
your barn is on fire!") from the home automation system to the "foreground"
user account as well as to iPhone etc.
Original comment by groble...@gmail.com
on 3 Apr 2013 at 3:37
Original issue reported on code.google.com by
dan...@growl.info
on 27 Jan 2012 at 3:23