checkHalfWidthPathSeg always enforce

Hi Lin,

Unfortunately I don't have that specific hotfix. I tried an earlier version, and saw the correct behaviour - it gives the popup, but still lets me do it.

Ah, hang on, I'd not twigged you were talking about stretching the path rather than entering it in the first place. You didn't say that in your first post (but you did say it later, so my apologies, I'd missed that).

There's a CCR for this,  767393. Unfortunately that's not fixed in IC615, as R&D ran out of time to get it done. There's a workaround, which is to create the "path" using pathSegs (e.g. use Create Wire), but we really should fix this, I agree.

Icons should not be the primary user interface. They are an alternative user interface. Now there have been occasions when we've messed up - but that's not the intention. I tried several versions of IC614, before and after the one you're using - and Connectivity->Nets->Show/Hide Current Incomplete Nets (or Selected Incomplete Nets) is there as a menu item. I think it wasn't in the past though - initially the lack of show/hide incomplete nets was an oversight - the assumption was that people would have the annotation browser up, and use that to toggle the incomplete nets. I think an icon was then quickly added, and the menu came back later.

If there are bugs with the workspaces, please contact customer support. Note you can use the F11 bindkey (by default) or the little eye window with an eye icon in the workspace toolbar, or  Window->Assistants->Hide All (or Show All) to toggle all the assistants on and off. Similarly you can create your own workspaces (and default workspaces) so that you have no toolbars at all, if you like.

There are different classes of users - some find bindkeys intuitive, some like menus, some prefer icons. The icons have tooltips over them so you can read (assuming you're not illiterate!) what they do, and then re-use them without have to go to multi-level pulldown menus. A lot of the point of having multiple input methods is to allow people with different levels of experience to have the ability to find the command they want, and also to provide a variety of input methods, which is important for RSI and so on. We should not be forcing anyone to have to use icons, so if you see something that's on an icon only, please let us know - I wholeheartedly support that functionality should be on menus too. Of course, if it's an assistant already, then it may not make sense to clutter the form with a menu as well, but for functions for the main canvas, I certainly agree.

Regards,

Andrew.

Hi Lin,

Unfortunately I don't have that specific hotfix. I tried an earlier version, and saw the correct behaviour - it gives the popup, but still lets me do it.

Ah, hang on, I'd not twigged you were talking about stretching the path rather than entering it in the first place. You didn't say that in your first post (but you did say it later, so my apologies, I'd missed that).

There's a CCR for this,  767393. Unfortunately that's not fixed in IC615, as R&D ran out of time to get it done. There's a workaround, which is to create the "path" using pathSegs (e.g. use Create Wire), but we really should fix this, I agree.

Icons should not be the primary user interface. They are an alternative user interface. Now there have been occasions when we've messed up - but that's not the intention. I tried several versions of IC614, before and after the one you're using - and Connectivity->Nets->Show/Hide Current Incomplete Nets (or Selected Incomplete Nets) is there as a menu item. I think it wasn't in the past though - initially the lack of show/hide incomplete nets was an oversight - the assumption was that people would have the annotation browser up, and use that to toggle the incomplete nets. I think an icon was then quickly added, and the menu came back later.

If there are bugs with the workspaces, please contact customer support. Note you can use the F11 bindkey (by default) or the little eye window with an eye icon in the workspace toolbar, or  Window->Assistants->Hide All (or Show All) to toggle all the assistants on and off. Similarly you can create your own workspaces (and default workspaces) so that you have no toolbars at all, if you like.

There are different classes of users - some find bindkeys intuitive, some like menus, some prefer icons. The icons have tooltips over them so you can read (assuming you're not illiterate!) what they do, and then re-use them without have to go to multi-level pulldown menus. A lot of the point of having multiple input methods is to allow people with different levels of experience to have the ability to find the command they want, and also to provide a variety of input methods, which is important for RSI and so on. We should not be forcing anyone to have to use icons, so if you see something that's on an icon only, please let us know - I wholeheartedly support that functionality should be on menus too. Of course, if it's an assistant already, then it may not make sense to clutter the form with a menu as well, but for functions for the main canvas, I certainly agree.

Regards,

Andrew.