-
Notifications
You must be signed in to change notification settings - Fork 90
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
Normalize coordinates on save #423
Comments
How to do this? |
Mouse-wheel helped. =) But it looks like it is a bug with Nodebox save ability. |
If you save the file and then reload it, zoom level will be reset and box will be lost again. |
Yes — NodeBox doesn't keep the location of where you zoomed. If you have nodes that you move outside of the standard box they appear to be hidden. In your case the node is at location A solution we do is to move the box back to the "reset" position. In your case it means panning the view a little bit "up" (so holding spacebar and dragging down), then moving the node down one or two squares. |
Move manually? Why don't adjust all coordinates to 0,0 coordinate on save? (another bug - holding spacebar with down works only for half of the second, then everything freezes) |
Saved nodes can be panned on save, but it looks like writer is not the best place to do this. |
"Panning" on save sounds interesting. However, what happens if the bounding box of available nodes is bigger than that of the view? Do we just make sure that the top-left node is on 0,0? |
If bounding box is bigger, Nodebox still resets view to 0,0 on load, so placing top-left node there helps to unwind the graph after this jump. |
Hmmm that could work.... |
I see the output, but graph pane is empty. =/ No output in terminal or console window.
barbox.ndbx.zip
The text was updated successfully, but these errors were encountered: