Messages

1

Suggestions and Requests / Re: "Show Realized Interfaces" - better

« on: August 24, 2006, 03:58:10 pm »

>> 1. ) Look at Element | Advanced | Override Implementation.

This is a totally different function.  The "Show" function controls whether a lollipop is shown on the class.  The "Override" function implements overrides in subclasses.

>> 2) You can use keyboard arrows to navigate the context menu.  Mind you, I can't find it in the context menu anyway.

The only way to reach "Show Realized Interfaces" is through the context menu (I'm pretty sure), so I don't know what you're thinking of... maybe you've confused "Override" with "Show" still?  Click on a class, now, without using the mouse, try to find a sequence of keystrokes that will lead you to "Show Realized Interfaces".

Here's how to reach it with the mouse:  
 1.) right click on class
 2.) Select "Add Embedded".
 3.) Select "Show Realized Interfaces".

>> 3) It seems to me that this is also something that doesn't make sense with multiple classes selected.

Maybe this is the "Show" vs. "Override" confusion again.  Example: I have six classes that all implement interfaces, and I want to show lollipops on all of them.  Given items 1 through 3 above, it's pretty tedious.  If multiselect worked, I wouldn't care as much about the other two issues.

-Ed Staub

2

Suggestions and Requests / "Show Realized Interfaces" - better UI,

« on: August 24, 2006, 11:17:47 am »

It would be nice if the class context menu item "Add Embedded...Show Realized Interfaces" was more easily used.  There are probably other commands in this category - if you address this, I'd look for the other cases too.

1.) Because it's only accessible as a context-menu command, the command can't be accessed from the Customize... UI, so it can't be put on a toolbar or bound to a key.  This is probably true of all commands that are on the context menus and not on the toolbar menu.

2.) Keyboard access does not work.  Try it.  Context-menu-key + B goes straight to a different dialog box, I think because there's no accelerator keys assigned to the rest of the keys in the submenu.

3.) There are a lot of actions that could be applied to multiple objects at once that aren't accessible from the context menu if you multi-select.  This is one of them.

Thanks,
-Ed Staub