suggested improvement for new device dialog

Posted on
Sat Sep 16, 2017 11:00 am
dduff617 offline
Posts: 339
Joined: Jul 05, 2006

suggested improvement for new device dialog

i occasionally find myself wanting to explore a plugin or consider creating a new device, then want to exit without actually creating one. or i start creating a device and either change my mind and don't get around to finishing. the current behavior is that when you hit the new-device button (cmd-shift-D), the device seems to get created when you make a selection from the type menu and i feel that this can be sometimes counter-intuitive.

examples:
  • if you just hit cmd-shift-D (new device) followed by cmd-w (close), nothing is created.
  • if you hit cmd-shift-D (new device) then select a "type" from the pulldown, but don't select a "model", then hit close, an incomplete new device is created with model "undefined".
  • if you hit cmd-shift-D (new device) then select any "type" from the pulldown, then decide to cancel the operation. you must hit close, then find the resulting device in your list of devices (it might be named "new device <n>" if you didn't change the name) , then hit delete, then confirm "are you sure you want to delete?" to delete the device.
  • if you hit cmd-shift-D (new device), then enter a type and model, and device name, then hit close (without doing any further device configuration), a device gets created. this device may be inoperative before being configured further, but it can be later edited by the user. so this may be considered desirable behavior.

to simplify, and to make this more understandable and predicable, it might be more natural if the new-device dialog had something like an ok/save/create button and a cancel button.

to preserve essentially the same semantics as the existing interface, the ok/save/create button could be grey'd out until the user makes a selection from the type menu. i suggest it might be good to also make selecting "model" and typing a device name be required before you can exit the dialog and create the device (to avoid creating inoperative devices with "undefined" type and also to avoid creating devices named "new device", neither of which seem very useful). to exit before these things are filled in or to cancel the pending device creation for any reason, you can hit "cancel".

Posted on
Sat Sep 16, 2017 11:24 am
matt (support) offline
Site Admin
User avatar
Posts: 18069
Joined: Jan 27, 2003
Location: Texas

Re: suggested improvement for new device dialog

Agreed. The peculiar behavior is related to how plugins need to be able to reference the device before the user has finished configuring it (in UI), so it gets added into the database a bit earlier than expected (by the user). We can improve that a few different ways, including by the logic of your suggestion.

Image

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 3 guests