mover() inconsistency
See original GitHub issue(Manually migrated from GitLab issue 3 reported by @kranich)
In Cinderella, mover()
yields the element which has last been moved. In cindyjs, mover()
yields the element which is currently being moved.
Hence, mover produces different behaviour on mouse up (_?_
in cindyjs vs. the element which has last been moved in Cinderella).
(Comment originally by @kortenkamp)
The Cinderella behavior is the preferred one, IMHO. Of course, one could create a workaround and store the current moving element, but this creates ugly code.
Also needs a comment from @richter-gebert
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
The EM Algorithm for Maximum Likelihood Estimation in the
Briefly, the mover-stayer model is a mixture of two independent Markov chains, one with degenerate transition probability matrix equal to the identity matrix...
Read more >Known Issues and Limitations: Data Protection for VMware V8.1
This document details the Known Issues & Limitations for IBM® Spectrum Protect for Virtual Environments: Data Protection for VMware V8.1.
Read more >How to move objects in Unity (3 methods with examples)
If you're trying to move an object without Delta Time, you're going to get inconsistent movement. ... void Update()
Read more >Chapter 7: Attitudes, Behavior, and Rationalization - Quizlet
It is aroused whenever people experience inconsistency between two ... The movers Howard hired ask him to post a positive Yelp review in...
Read more >Quantitative color profiling of digital images with earth mover's ...
Earth mover's distance (EMD) (Rubner & Tomasi, 2013) or another ... TRUE for extractClusters() will guarantee that bins are comparable, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
And let me add something else: It is essential to receive the last mover() in the mouse up event! Just consider the following code:
In mouse down:
In mouse up:
This is not uncommon. So… I am strongly opposed to setting
mover()
tonull
already in mouse up. It might be ok after mouse up.It was decided that the CindyJS behavior should stay, and that Cinderella should use the CindyJS semantics when executing the code as CindyScript 3. The main benefit is that this allows scripts to easily detect whether some element is being moved or not. The woraround to store the mover in a variable is easy enough that essentially no functionality is lost, even if some code may need some adjustments.