Bug 447668 - Mapping/precondition checks feedback is not displayed when tools from palette by drag and drop
Summary: Mapping/precondition checks feedback is not displayed when tools from palette...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-10-17 05:22 EDT by Maxime Porhel CLA
Modified: 2015-10-29 10:41 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Porhel CLA 2014-10-17 05:22:49 EDT
When a user select a MappingBasedTool and hovers the diagram, Sirius check the tool definition i.e. the mapping structure and the precondition and display the 'forbidden' icon if the current target of the tool is not valid regarding the definition of the tool.

When the user click on a tool and drag it on the diagram, no feedback is displayed for invalid targets (mapping or precondition). 

However when the user drop the tool on an invalid target, the tool is not executed.
Comment 1 Niels Brouwers CLA 2015-10-27 09:07:24 EDT
We have created a feature to prevent a modeler to change anything to an 'external' model element. With external, we mean that a node on a diagram represents a semantic model element that is contained in a different model than the one that contains the semantic model element of the diagram. The functionality is heavily relying on the precondition of the tools specified in the diagram specification file (.odesign file). 

This bug prevents the user to receive clear feedback that a specific operation can not be performed. Currently, the user gets the impression that the operation can be performed on an 'external' model element, but in fact the operation is not executed. Instead, as suggested by Maxime, it would help a lot to show the 'forbidden' icon in such situations, indicating to the user that the operation is not allowed.

I notice that this bug has been reported a year ago, but is not solved yet (exists at least in Sirius v3.0.0). Would it be possible to solve this bug in short notice?
Comment 2 Laurent Redor CLA 2015-10-29 10:41:08 EDT
We are aware of this but have no plans to work on it in the following weeks.
That said this bug can move forward if you provide a fix for it (see the Contributor Guide) or you contact Obeo for sponsored work.