Usability: enable the on/off/reset buttons at all times

[GoogleCodeExporter]

There are times when the top row of buttons (on/off/reset, etc.) are disabled 
based on what hardware elements have focus.  Clicking on the main machine or 
the monitor in the left column makes them enabled, but clicking on any other 
hardware element (slots or peripherals) makes them disabled.  I suggest that 
they should always be enabled.

Why?

The top line buttons should always have power over the emulator, no matter what 
happens to be selected down the left column.  It doesn't make sense to only 
have those options open to you when the system or monitor is selected.  You 
should always have those options open to you.

Original issue reported on code.google.com by David4...@gmail.com on 18 Jul 2012 at 1:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Example of what I'm talking about: you mean you can make the monitor sleep, 
wake up, or reset?  But you can't make the paddles do the same?  ;-)

Original comment by David4...@gmail.com on 18 Jul 2012 at 2:00

Attachments:

• SleepMonitor.png
• NoSleepPaddles.png

[GoogleCodeExporter]

You won't believe it, but I did put some thought in this :-):

There are devices that you would want to turn on/off or reset, for example a 
printer or a second computer. That's where this idea came from. Of course there 
is the opposite train of thought, which is that there is a single source of 
power/reset within an emulation, so this is very debatable! :-)

Original comment by mre...@gmail.com on 18 Jul 2012 at 5:31

• Changed state: Accepted

[GoogleCodeExporter]

I do believe it!  It would in fact be cool if you could turn various pieces on 
and off, especially the things that had individual power switches.  But the 
reality is that even with the monitor selected, it's the computer that gets 
reset or powered up or down.  In order to keep the ambiguity out of people's 
minds, though, the buttons would need to be in the context of the peripheral - 
i.e. next to it in the tree, rather than at the top.

Original comment by David4...@gmail.com on 18 Jul 2012 at 5:36

[GoogleCodeExporter]

Well, the standard GUI language calls for a toolbar at the top, I don't think 
it's a wise idea to break that.

Anyway, most of the time you are using the monitor view, and this one is always 
connected to the computer.

Do you have any other ideas in mind?

Original comment by mre...@gmail.com on 19 Jul 2012 at 3:26

[GoogleCodeExporter]

No other ideas yet.  Just that the toolbar at the top should be used/enabled 
consistently.  If it controls the emulator, let it control the emulator.  If it 
controls the context of the selected object, then let it control that.  Right 
now, it controls the emulator when either the machine or the monitor is 
selected; otherwise, it's disabled.  So it's currently inconsistent.

Original comment by David4...@gmail.com on 19 Jul 2012 at 3:32

[GoogleCodeExporter]

I disagree.

For example, in a mail application the toolbar options for reply/reply 
all/resend are context-dependant (they depend on the selected message), just 
like the reset/restart options in OE are context-dependant. But there is 
something that feels wrong and different in comparison to the mail program case.

Original comment by mre...@gmail.com on 19 Jul 2012 at 3:46

[GoogleCodeExporter]

Oh, I just understood your point!

And yes, you are right. Sort of, because the way it works internally is that 
the monitor forwards the power/reset commands to the emulation.

So, do you think it is best to keep power and reset a global property? Just 
like in real life, where you use a power extension with an on/off switch, and 
that controls power to ALL devices? Makes sense to me.

And if you have a device like a printer that can be reset individually, do it 
through the printer window?

Original comment by mre...@gmail.com on 19 Jul 2012 at 3:53

[GoogleCodeExporter]

Original comment by mre...@gmail.com on 19 Jul 2012 at 3:55

[GoogleCodeExporter]

I would say that there should be a general-purpose emulator controller at the 
top at all times: stop/start, pause, reset, reboot.  The controls, even power, 
for individual elements could be in their normal adjustment area under 
"Options."  Though, in reality, I can't imagine why someone would want to power 
a virtual printer off - and it could potentially cause confusion.  Imagine the 
defect report: "I added a printer - why isn't my PR#1 output showing up?!?"

Original comment by David4...@gmail.com on 19 Jul 2012 at 2:57

[GoogleCodeExporter]

The edict has been pronounced. Global power/signals are the way to go :-).

Original comment by mre...@gmail.com on 19 Jul 2012 at 3:21

• Changed state: Started

[GoogleCodeExporter]

Original comment by mre...@gmail.com on 20 Jul 2012 at 7:46

• Changed state: Fixed