Martin Ziel

``` //main.gravity func main() { var button= ButtonWidget(100, 100) getWindow().addWidget(button) } //button.gravity class ButtonWidget { var _x; var _y; func init(x, y) { _x = x; _y = y; }...

I'm not sure if we're talking about the same thing. What I mean is to change the code of a running Gravity VM. 1. Load and execute button.gravity and main.gravity...

Ok, but that means you have to write your changes, write the bind instruction and then execute it to be changed, am I correct? The purpose of hot reload is...

I was expecting that a few things might not work correctly, and some problems were introduced when I added the undo/split/delete/join functionalities. I'll fix the problems you've mentioned.

The previous problems have been fixed. I would appreciate it if someone could test the new version if he or she spots any new problems I didn't catch.

- This problem seems to occur when the bezier segment is straight. In that case, the mMapScene->items(pos) call returns no object. The problem can be alleviated by using a rectangle...

Unfortunately, the commit was immediately pushed.

I usually don't rewrite history out of principle, but I understand that you want a clean history and squashed the commit.

@Darky-Lucera I haven't had QT experience before this PR either :smile:. Having looked at the other kind of splines, they would definitely be a nice addition and easier to implement...

No problem, I'll fix it when I take care of the click area issue. I hope I'll get to fix it soon.