V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Questions or discussions about the Titan and classic consoles and software.

Moderator: Moderators

danhoff
Posts: 38
Joined: 04 Oct 2014, 23:35

V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Postby danhoff » 04 Oct 2014, 23:58

Default 'delete' behavior, under User Settings, when changed to 'Unassign' rather than 'Delete,' doesn't seem to apply to cues. So, on a Tiger Touch, with the Show Library open, I am able to watch whether items are deleted or go into the 'Unassigned' category, and regardless of the setting of this option, they are deleted.
User avatar
niclights
The eManual
Posts: 4461
Joined: 24 Sep 2004, 01:06
Location: UK

Re: V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Postby niclights » 05 Oct 2014, 00:31

Do you mean playbacks or cues from cuelists? When I test deleting playbacks they move to unassigned as expected. There is currently no option to unassign individual cues.
danhoff
Posts: 38
Joined: 04 Oct 2014, 23:35

Re: V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Postby danhoff » 05 Oct 2014, 19:12

No, I was having the issue with playbacks, i.e. single cues on a handle.

Here are the steps to reproduce the issue, which I just did in Titan Mobile Simulator:

Start a new (blank) show.
Record, select a playback.
Open Workspace Window --> Show Library
See the cue you just recorded, on Page 1 of Playbacks.
Hold AVO, press User Settings.
Change option "Delete Default" from "Delete (2/2)" to "Unassign (1/2)".
Press Delete, then blue button for the playback you just recorded, then softkey 'A' for 'Confirm'.

Perhaps this feature just needs clarification, I just read the release notes for v8 again and found this:

"Unassign handles: When deleting a handle there is now an additional softkey option to unassign rather than permanently delete. To accompany this there is also a new user setting to determine the default action for double-tapping a handle when deleting. When an item is unassigned it will remain available in the show library."

The double-tap behavior does change as expected, however, the prompt still reads, "Delete Cue 'Cue 5', please select again to confirm delete." even when the default has been changed so you're actually unassigning by double-tapping. Perhaps it would be clearer if, when this setting is toggled, the behavior that is 'confirmed' in either case is the one that the default is set to, and the option on Softkey B is the alternate case?
User avatar
niclights
The eManual
Posts: 4461
Joined: 24 Sep 2004, 01:06
Location: UK

Re: V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Postby niclights » 05 Oct 2014, 19:36

I agree it would probably be clearer if the prompt text changed to read 'press again to unassign'. Not convinced the softkeys need to change though. I think if you are a double-tapper you will set the option to your preference and then never read either the prompt or the softkeys again. However, if you are not a double-tapper then it might be confusing if the softkeys swapped.
danhoff
Posts: 38
Joined: 04 Oct 2014, 23:35

Re: V8 bug? Default 'Delete' Behavior = Unassign, doesn't

Postby danhoff » 05 Oct 2014, 19:53

Certainly, now that I understand the behavior, I won't make the same mistake again. But clearer labeling would help avoid the confusion in the first place, and would be helpful even for experienced users when they have a guest LD running the desk...etc. 8)

The prompt is definitely out of date with the new setting....the softkeys being context-sensitive to that option in user settings would be a nice bonus.

If anything perhaps Softkey A could be made more clear by saying 'Confirm Delete' rather than just 'Confirm,' as it'd be even more unclear what you are confirming if the prompt changed to say "Unassign Cue 'Cue 5', please select again to confirm unassign."

Who is online

Users browsing this forum: Google [Bot] and 40 guests