Bug 415595 - various usability bug in model edition
Summary: various usability bug in model edition
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 0.10.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 10:50 EDT by Nicolas Boulay CLA
Modified: 2017-09-08 09:57 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Boulay CLA 2013-08-21 10:50:18 EDT
Copy-past/drag&drop problem :
- It's impossible to copy/paste properties in the model explorer or in a diagram, to an other model. The copy should be manual.
- The type of the properties fields can't be copy/pasted.
- You can't drag&drop properties from the model explorer to a diagram, if the mouse travel over an other model (if 2 model is open side by side). The mouse should travel thought the properties windows (for example), to avoid the bug.

Properties :
- Sometimes a little "+" is added to the properties in the model explorer without signification (2 properties with the exact same values but different name, one have the little "+", the other doesn't )
- The exact same properties of a class, could be drag&Drop 2 times in a diagramm box.

About the "comment" box :
- Sometimes in a comment box, the upper lines of a multiline comment can't be seen when editing.
- Sometimes line return are displayed in editing mode, that does not existe in view mode.
- When a comment box size is changed or moved, the "yellow shadow" have the width of the box at the creation, not the last one.
- When the comment box is at a bottom of a page, when a new line is created by hitting "enter", the line is under the visible canvas. Then you should take the mouse, and clic the arrow. You have to do it a each new line, because you can't make a "big move", or you can create a dummy object under the comment box. The canvas should go done to follow the mouse like the web navigator does.

Nice to have :

About resizing object :
- When a box is resized, the connector should not moved, this brake nice horizontal or vertical lines, the connector could also came accross other boxes.

"compartment to display" :
- When there is many selection to filter "compartment to display", i expect to have a single box for each compartment, and not every element displayed. To remove a single kind of block, i need n clic instead of one.
- It should be possible to save a defaut setting.

Type of the properties :
- When the filter is used in the type searching windows, the tree are not open. To choose string or real, you must clic 2 more times. The tree should be "open", to save this clic.
Comment 1 Camille Letavernier CLA 2013-08-26 08:15:49 EDT
> - The type of the properties fields can't be copy/pasted.

This doesn't really make sense to me. If you select the type of the property and copy it, how would you know whether you want to copy the classifier itself, or the "type" value of the property? It seems easier to select a set of properties and set their type from the properties view.

> - You can't drag&drop properties from the model explorer to a diagram, if the mouse travel over an other model (if 2 model is open side by side). The mouse should travel thought the properties windows (for example), to avoid the bug.

Stack trace when hovering a different model during the drop:

!ENTRY org.eclipse.ui 4 0 2013-08-26 14:08:11.838
!MESSAGE Unhandled event loop exception
!STACK 0
java.util.MissingResourceException: The string resource 'platform:/resource/some_project/model.di' could not be located
	at org.eclipse.papyrus.infra.services.resourceloading.impl.ProxyManager.getEObjectFromStrategy(ProxyManager.java:167)
	at org.eclipse.papyrus.infra.services.resourceloading.OnDemandLoadingModelSet.getEObject(OnDemandLoadingModelSet.java:77)
	at org.eclipse.papyrus.cdo.core.resource.CDOAwareModelSet.getEObject(CDOAwareModelSet.java:58)
	at org.eclipse.papyrus.uml.diagram.common.listeners.DropTargetListener.getObjectsBeingDropped(DropTargetListener.java:86)
	at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramDropTargetListener.updateTargetRequest(DiagramDropTargetListener.java:197)
	at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramDropTargetListener.isEnabled(DiagramDropTargetListener.java:213)
	at org.eclipse.jface.util.DelegatingDropAdapter.updateCurrentListener(DelegatingDropAdapter.java:365)
	at org.eclipse.jface.util.DelegatingDropAdapter.dragEnter(DelegatingDropAdapter.java:128)
	at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:60)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	[...]	

> - Sometimes a little "" is added to the properties in the model explorer without signification (2 properties with the exact same values but different name, one have the little "", the other doesn't )

I don't understand this one. Do you have the steps to reproduce it?

> - When there is many selection to filter "compartment to display", i expect to have a single box for each compartment, and not every element displayed. To remove a single kind of block, i need n clic instead of one.

Did you try "Propagate selection to elements of same type"?

- Select N blocks
- Show/Hide compartments
- Choose the compartments you want to display/hide on the first Block
- Click "Propagate selection to elements of same type"
- Press OK

All selected Blocks will have the same set of compartments. CSS Stylesheets should also provide a much more efficient way to do that (CSS Support for compartments is planed for late 2013)

> - It should be possible to save a default setting.

You can do that from the Diagrams preferences page (Or CSS when compartments will be supported)



Other bugs are confirmed
Comment 2 Nicolas Boulay CLA 2013-08-26 08:45:56 EDT
1) Type is shown as a text, you expect to copy/paste this text in a other properties. Setting one by one could be slow and painfull.

3) I juste create a model, with some class and some properites. Sometimes a little graphical "+" is added to the property symbol.

4) I haven't try "Propagate selection to elements of same type", this is not a common/expected function. But it works.

5)ok for the "Diagrams preferences page", but button "set as default" is quite common in GUI. This is easier to put this kind of button, where the setting is used rather in a udge option panel.
Comment 3 Alain Le Guennec CLA 2013-08-26 08:51:07 EDT
As for the "+" decorator in the browser for properties,
it seams that it appears if visibility is *explicitly* set to "public",
but not if visibility *defaults* to "public" because it is not explicitly set.
So to reproduce, simply set the visibility to anything but "public", then back to "public".
Comment 4 Camille Letavernier CLA 2013-08-26 08:59:11 EDT
3) For default visibility kind, see Bug 415141: [Model Explorer] New property is not graphically displayed as public