This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I am experiencing some perplexing behaviour with my diagram nodes. In some cases when the user clicks the up/down/right/left arrows on the keyboard the nodes will move in the direction of the arrow. However, this does not seem to happen all the time. In some cases the selected node will change (to another node in the direction of the arrow). I can't figure out why in some cases it will do one thing, and in other cases it will do something else. Ultimately I would prefer to turn off the node movement. I have some nodes that I particularly do not want the user to move. Looking at the source code, I don't see an easy way to do this. I am already registered to the BoundsChangeRequestedEvent event, and when this movement occurs, this event is not triggered. Really strange. Any help you can provide will be very helpful. Thanks |
|
|
I think I have figured out the logic behind the decision making process, but it does not make it any less weird. Basically, if you click the left arrow and there is a node connected to the left of the selected node, then the node to the left will become the new selected node. (same for the other directions). However, if the selected node is the 'left-most' node, then the node will move to the left. So, not random, but still. |
|
|
Hello eliz, This weird logic is caused because the DaigramSurface is a ListBox, and nodes are list box items. The ListBox is using it's keyboard logic to select items, but when there are no items to select, the keyboard logic bubbles to the move thumb of the selected node which causes it to move. This is something we should be able to resolve which I will be able to look into next week. -Jason Fauchelle |
|
|
Hi eliz, This problem has now been resolved and will be available in the next nightly build. Let me know if you have further questions. -Jason Fauchelle |
|
|
Great. I just got the latest release. Thanks for the fix. |
|