Hello,
This is better - personally I would color the camera and mic icons
that are activated, so they look "ON" - (without the slash of course)
- and to indicate the "OFF" status - it is fine - with the slash.
For example, when you hover over (or mouse over) the tiny speaker icon
in the dragable user rectangle we see the orange-colored old-fashioned
microphone image pop-up - this is excellent. I would also have theat
tiny speaker icon in the dragable user rectangle in orange to indicate
its state is "ON" when it is on - the other two tiny icons (refresh
and minimize) at the top of the dragable user rectangle are fine in
grey since they are settings to change not states and users know what
to expect with them.
This is my advice since you asked - I'm more concerned with
fonctionality! It is working well.
One question - I have tested this extensively in Chrome adn I notice
that if one sets the volume of teh microphone different than 50 (in
the tiny icon in the dragable user rectangle) -each time I refres the
user it si reset to level 50. Is this desired? Wouldn't it be better
to keep the last user volumn settings through a "refresh" since users
will most probably use the refresh to see or hear another user who may
have changed the state of their camera and microphone. This is just an
idea - it is OK as it is since it's easy to reset it.
Thansk for the good work. I'll test this on FF adn Edge and if there
are any problems will reply again.
Ed
Quoting Maxim Solodovnik <solomax...@gmail.com>:
The demo is updated
Is it what you want? :)
On Fri, 27 Mar 2020 at 20:58, Maxim Solodovnik
<solomax...@gmail.com> wrote:
done will update demo as soon build will be ready
Will appreciate if you can test it :)
On Fri, 27 Mar 2020 at 20:08, Maxim Solodovnik
<solomax...@gmail.com> wrote:
it seems icons have to be changed ... give me couple
of minutes
On Fri, 27 Mar 2020 at 20:06, Marcus Schulz
<m...@polarnetworks.de> wrote:
I experienced the same with these buttons. I had to read the
tooltip also before clicking.
Am Freitag, den 27.03.2020, 11:31 +0100 schrieb Juan
Antonio Moreno Carmona:
Well, for my part I agree with the suggestion provided by Ed. I
think it is more intuitive. Maybe other users can contribute
their opinion. El 27/3/20 a las 11:29, BBS Technik
escribió:
I think it is a good ideal to swap it. Regards Ed
Gesendet: Freitag, 27. März 2020 um 11:22 Uhr Von:
"Maxim Solodovnik" < solomax...@gmail.com
> An: "Openmeetings user-list" <
user@openmeetings.apache.org > Betreff:
Re: A general Suggestion from a tester who'd like easier user
experience with the software Well To
implement this I need to swap 2 lines of code No
problem at all if community will approve this On
Fri, 27 Mar 2020 at 17:19, <
i...@bureau-de-poste.net > wrote:
Hello everyone, I love this software 5.0.0 M3
(running on Ubuntu 18.04) with KMS 6.13 A few
questions and an important suggestion: 1) I have
been unable to install this on debian buster so that it works
well - can this be done? How? We'd like to be able
to use this on buster. 2) When having
inexperienced users test our M3 version (and when testing
the M4 version -the same problem exists):
The left-hand user column symbols for camera and microphone
indicate to-do action links, and I think they
should indicate actual states - because this is
more intuitive and is what users expect. So, I
suggest instead of showing a microphone with a red circle
with a white "x" in it in M3 or an orange
old-fashion mic symbol with a slash through it in
M4 to indicate that the mic is "ON" and that you have to
click on it to turn it "OFF", I suggest that exactly
the opposite be shown: the actual state of the
feature - that a slash through a symbol (perhaps in
grey to double indicate it is off) indicates that it is
"OFF" and a colored on symbol or icon without a
slash indicates that it is "ON" The same
suggestion for the camera. 95 % of user problems
that I have encountered result from this. Users see
something with a slash through it and they think that means
that it is "OFF" or not activated. Why not give
users what they expect intuitively rather than
force them to behave different than usual for this app?
I love this app/project, and this is just a friendly
suggestion, not criticism. best to all
Ed
-- WBR Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
