Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wiring Editor: strange behaviour modifying connections #175

Closed
aarranz opened this issue Apr 29, 2016 · 0 comments · Fixed by #179
Closed

Wiring Editor: strange behaviour modifying connections #175

aarranz opened this issue Apr 29, 2016 · 0 comments · Fixed by #179
Assignees
Milestone

Comments

@aarranz
Copy link
Member

aarranz commented Apr 29, 2016

Example, consider we starts at this point:

captura de pantalla 2016-04-29 a las 16 19 33

The problem raises when the user modify the connection between the NGSI Source operator and the Map Viewer widget to be exactly the same than the one currently used in other behaviours between the NGSI Source operator and the Spy Wiring widget:

captura de pantalla 2016-04-29 a las 16 09 27

captura de pantalla 2016-04-29 a las 16 10 14

If the user finishes the drag and drop operation in that step, the wiring editor adds the connection NGSI Source-Spy Wiring connection and maintains the previous connection:

Although this operation is by itself is strange (I think only expert users will try to do it), the behaviour exposed by the Wiring Editor is not any of the expected ones. In my opinion, there are two options:

  • Adding the NGSI Source-Spy Wiring connection to the current behaviour and removing the previous connection. I prefer this option because I think that make sense and can be view as a shortcut.
  • Or ignoring the user and doing nothing.
@aarranz aarranz added this to the May 2016 milestone Apr 29, 2016
jpajuelo added a commit to jpajuelo/wirecloud that referenced this issue May 3, 2016
aarranz referenced this issue May 4, 2016
Wiring Editor: modify connection and then drop it over connection on background
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants