I think it would be a good addition to add "=" as a keystroke that moves
the focus to the Intensity field in the most recently touched control
window. Although LCEdit+ 3.0 is a little better at it, sometimes after
selecting a group or fixture the Intensity field doesn't get hilited.

I still am campaigning for the ability to say "l3=100%" in the command
linel as a shortcut for setting the Group Intensity field of group 3 to
100%. It may not be absolutely necessary (there are other ways of doing it
nearly as fast) but it's a User Interface issue that it doesn't work. This
last week I have been teaching my co-lighting-person (I'm at a high school
so we put aside the "cue as fast as possible" method and go for the "teach
someone who doesn't know how to work the board how to work it") She has
tried twice to do either kX=XX% or lX=XX%. When I tell her it doesn't work
like that, she says "well that's stupid."

Third feature request- Could you add a preference that sets the "default
entry number system?" While it's nice to be able to set the values by DMX
value (i.e. 255 instead of 100%, 128 instead of 50%, etc) most people are
going to want to use percentage instead. You can train yourself to say
"50%" but it would be easier if we could just say "we always want to use
percentages unless we specify otherwise." Again, there are ways around it,
but the central idea of User Interface Design is to make everything as
easy as possible for the user, even if it means saving them one keypress.

Feature request #4- Could you add tooltips on all the iconic buttons on
the Control Window in LCEdit+ 3? I was used to LCEdit+ 2 and had finally
figured out what the abbreviations meant; now I use LCEdit+ 3.0.1 and I'm
having to flip to the manual every time I need to change a layer setting.

Mini Feature Request #5- Can we resurrect something like the Channel
Enable button? I know you can just select all and hit Enter, but that's a
little less clear than a real "Enable" button. This one isn't that
important, I think I mostly just have to get used to the change.

Feature Request #6- Can we have some sort of confirmation that things like
"Delete Cuelist" in the Script Editor have completed successfully?

Feature Request #7- Can there be a checkbox in the Script Editor called
"Show Scene Data" that determines whether or not it will actually download
and print out all of the scene data for every scene? I know it's possible
to just download the step information without downloading the CONTENTS of
each scene as well. When doing theater, I don't use the Tracking features
of the console and enable all of my channels 1-96. Having to wait for the
Script Editor to display 30 cues that have 96 channels each makes using
the script editor a huge hassle. It takes a good 10 seconds to download
and show that much data.

Feature Request #8- Can there be a periodic task executing that adds a
carriage return to the little error message box in the bottom right of the
control window? Either that, or timestamps on the messages that appear
there. The problem is that I may do something that causes an error to
appear, and then forget about it. I try to do something else later and I
still see the first "Command Failed" down there and I don't know whether
or not it was from my most recent request. Another option that might work
out instead of timestamps is to add a "Command Succeeded" message that is
shown whenever a failable command (e.g. deleting a cue, adding a cuelist,
replacing cues, etc) runs successfully. In this manner I can look down in
the bottom right and not have to worry that the LanBox didn't do what I
told it to do.

Feature Request #9- This one is a little bigger than the others, but...
can there be an option to switch the interface into "Show Mode" that would
cause all the colors to be toned down and inverted such that the majority
of the screen is black and interface is not overly bright? We've already
turned down our monitor's brightness and contrast all the way, but it's
still a little bright due to the white nature of the interface. "Show
Mode" could also desist from calling the System Beep and just flash the
screen instead. If it's easier you could just set the System Volume to 0
as a convenience. Make sure that is a preference though, since some might
prefer to use headphones?

Feature Request #10- This might require firmware changes but could be
worked around effectively in software: Is it possible to have an option
somewhere that after completing moving through a cuelist, instead of
returning to 1.0 it would move on to the next lowest numbered cuelist's
first cue? For example, if I am at 1.12 and 1.13 does not exist but 2.1
does, pressing "Go" on 1.12 would automatically move to 2.1. I know I can
do this with a cue at 1.13 that says "Go 2.1" (which is what I've done in
the past) but the downside to this is that it does not work in Edit mode,
so when we're still working on cueing the show we have to manually type
"g2.1". In the converse direction, pressing "previous cue" while at 2.1
would move backwards to 1.12.

Off to a 10:30AM Into the Woods call (performances this week, if you're in
Boston area and feel like seeing it, give me a mail for details)

• Feature Requests, Fokko van Duin
  • (- current message -), Fokko van Duin
    • Re: Feature Requests, Todd Lipcon
      • Re: Feature Requests, Fokko van Duin