I agree that usage data would provide an important missing piece to
these discussions. I proposed a solution previously but not in this
forum: Basically we could easily add a logging call to the base class of
the component library that records a count for each human action on each
UI element. T
I am thinking that this little issue we are discussing is a symptom of a
systemic problem: how a UI is created and how it evolves. So it probably
requires a new thread, but for continuity am keeping it here.
I think we should try to find a generic way that if applied, might actually
reduce the 'no
Somehow I think it should go into the voice chat tab of the preferences
dialog along with the rest of the voice preferences. I have reason to
believe that many voice users become familiar with that dialog.
I've been selling a LSL based lip sync system for over a year now and it has
a semi-transpare
I'd like to see an implementation of turning on and off the lip sync
feature that can be user tested to demonstrate that a new user of SL
could be instructed to "Turn off the moving lips" and easy turn the
feature off within 30 seconds or so.
I agree that a software developer, or someone who
I think that right direction is to assume that the majority of usage
would favor having it on, but that it should be easy to turn off.
Ron Blechner wrote:
We are still at the point where the 'uncanny valley' nature of the feature
can make it unnerving, and that problem is unlikely to be easil
Jumping in here on this conversation..
I am finding it incredible that a new feature would be suggested, be
enabled by default, and then have it decided to not have a way of
disabling the feature in preferences because someone thinks
preferences menu is so crowded. If the lip sync "featur
Q Said...
"Given the excessive complexity of the preferences dialog already, we
should take every opportunity to remove things from prefs, and there
should be a VERY high bar for adding anything to prefs. It's all too
easy for open projects to grow massive preferences systems and
configura
Perhaps the basic direction that this seems to be going in is that the
preferences system needs a hard look at. Many applications have an order
of magnitude more options than the SL viewer -- but their preferences UI
and the organization of preferences and categories of preferences (and
sometim
Yeah, it'd be like saying, "Let's not put cruise control in a car
because we can't figure out where to put the button." I don't see the
need to put it in preferences at all, as it's such an integral feature
with voice. But that question seems ... secondary ... to whether
lipsync is on by default.
Gordon, let's look at history. Color TVs. In particular, evolution from
black and white TV to color TV. My grandma used to have a color TV set. It
had all kinds of controls that I cannot dream of having today. The controls
reflected the unanticipated technological features that got injected into
th
Kent, then don't put it on by default. You can't really have it both ways,
if you have it on by default then there has to be an easy way to turn it on
and off and advanced is not an easy way. I agree that prefs is already
overcrowded but if you can't spare room in prefs for new items then maybe
S
I would like to know what happened exactly, at first it worked perfectly
for me, then it stopped being supported cause it was crashing some
people, then it started working worse and worse for me and eventually I
couldn't even find it on the client at all. Is any Linden around that
was around back w
12 matches
Mail list logo
