Adds additional mouse related functionality to MV including drag & drop. · By
Thanks! Now it works! But there's another thing... I don't know if this is an issue. So, when I drag an event with <draggable> tag in its notes and with random/autuonomous movement activated, it goes faster and it doesn't stop moving while it is being dragged. Same thing happens when "stepping" is activated in the event options. Then, when I place the event, it goes back to normal speed and normal frequency for both stepping and random/autonomous movement. This issue doesn't appear if the event doesn't have "stepping" option activated or if it doesn't have a random/autonomous movement. It would be nice if the event continued to step while it is being dragged if "stepping" option is ON, but its frequency/speed shouldn't go faster. And if the event has an autonomous movement, it should stop to move completely while it is being dragged (except for "stepping" animation if that's ON in the event options) until it is placed.
The speed concern you're having isn't related to a bug. The reason the object's position is able to keep up with the cursor's sudden position changes reliably is due to a tied-in increase in movement speed. Otherwise it would likely appear as if the object is following the mouse & playing catch up vs being dragged by the cursor. Keep in mind that this plugin is actually emulating standard drag & drop. It's not unlocking a built-in capability. That fact is why it can do so much more like manage location by tile and snap into place & even work with events & other objects without issues. Pausing autonomous movement during drags should be easy enough to incorporate I believe. I'll look into that. There is no way to have it continue stepping without the movement speed being affected though for the reason I mentioned above. At best I can have it disable stepping when being dragged to avoid the speed-up effect being seen.
I've added the feature of pausing step movement & autonomous event movement on drag to versions 1.29 & 1.69 which are now posted. Once again I can't make it an option to let stepping remain enabled while dragging without the speed suddenly picking up so I think having it pause instead is the best trade-off. Since I typically code most things from scratch while using events mainly as placeholders, I had no idea about the autonomous movement issue tbh but it was relatively easy to get fixed. It works on my end at least.
Ok so, it works partially. The autonomous movement pauses well if you place a draggable event on a tile in which there isn't any other event, but if you place a draggable event over another event, the draggable event goes back to its position and the autonomous movement doesn't resume and it remains paused. I noticed that this issue doesn't appear if you set Stackable Object to "true" in the plugin parameters.
I'm sorry if I'm bothering you, but maybe I found another little issue. So, when I drag a draggable event over an impassable tileset (not event), the draggable event doesn't snap back to its position and it remains blocked over the impassable tileset without moving at all. You can encounter this issue if Stackable Objects is set either to true or false.
Re-uploaded the latest versions again. I added a new feature to both that blocks objects from being dropped on impassable tiles now. I fixed a typo I made in the last update & I'm hoping that fixed the autonomous movement issue on your end. Even with the typo it already works right on my end for whatever reason. As soon as an even snaps back it starts moving again. It also works with stackable switched on for me. The events start moving after the drop. Not sure why its not working for you unless maybe I uploaded the wrong file before. Try it again.
I re-downloaded the file. Now the draggable event snaps back to its position if it is placed over an impassable tileset, but the autonomous movement remains paused. I don't know why it is not working for me, but it is working for you. I recorded a little gif to show the issue: https://imgur.com/tVMfFd9
Ok, so after updating my test project files to 1.6.2 I was able to reproduce the issue. Seems to have been cause by a typo. A missed capital letter in a variable name to be exact, but fixing that seems to have once again fixed the issue on my end. Try re-downloading the file again & let me know if it doesn't work.
