Warning - Please Stop the Host ...

[SteveJ_01]

Hi,

The message

WARNING Please stop the host or unlock from it before saving!

(and similar for other operations) also pops up un-altered when the user has the Preview feature running.

This can send the user off on a chase to figure out the situation with the transport of the host and this can becomes quite confusing and time-consuming when the transport of the host is clearly off and yet every operation attempted keeps popping up this warning.

Yes, ideally the user would perfectly manage going into and out of Preview, but in the real world (I testify!) it can be easy to overlook that Preview is on.

So, my suggestion is, if it is possible for JS to detect that the *real* reason for not being able to proceed with an operation is that Preview is on, then a specific message to that effect would be superb.

OTOH, If the nature of things is that this isn't really detectable/distinguishable to the program, then I suggest adding the text "(Also confirm Preview is Off)" to the warning.

Thanks!

[Azimuth (Archive)]

Perhaps just simply[b:4c214a1d42] "Please stop playback before saving"[/b:4c214a1d42] That would cover it all I think.

[SteveJ_01]

Perhaps just simply[b:6e1bdfced4] "Please stop playback before saving"[/b:6e1bdfced4] That would cover it all I think.

Logically at a meta-level that may be true, but "playback" has more than one potential source and that is at the core of my point here.

IMO, the goal should not be to pose a puzzle ("Where the heck [i:6e1bdfced4]is[/i:6e1bdfced4] that playback coming from?", or even "What playback?" since in fact the user may be actually be experiencing silence (I testify!) for any of several reasons), but rather either to a) automatically detect the actual issue, or b) verbally (textually) point out [i:6e1bdfced4]all[/i:6e1bdfced4] the possibilities so the user can check them directly w/o mystery.

Maximum value should always be placed on the user's time, IMO. Aiming to make messages as short as possible to save memory is 1980's-style thinking!

Assuming they know something they might not always puts the user's time at risk relative to simply telling them what they need to know at the point they need to know it.

Philosophical, I know, but I'm trying to both save the days and hours of user's lives [i:6e1bdfced4]and[/i:6e1bdfced4] reduce the # of support requests you get presented with. Worthy goals, I hope you'll agree. 8)

[Azimuth (Archive)]

"What playback?" since in fact the user may be actually be experiencing silence (I testify!) for any of several reasons)

Excellent point, I hadn't thought of that.