Skip to content
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

Configurable default new file position. #551

Closed
arthurwolf opened this issue Dec 8, 2019 · 3 comments
Closed

Configurable default new file position. #551

arthurwolf opened this issue Dec 8, 2019 · 3 comments

Comments

@arthurwolf
Copy link
Contributor

When importing a new file, it is always automatically positioned in the top left of the machine. However, on our machines, this means users always have to move the file/object to the lower left of the machine instead.
It would be great if there was a configuration option that would allow defining which corner is the default position for new files.
Thanks!

@mgmax
Copy link
Collaborator

mgmax commented Dec 31, 2019

Currently, VisiCut uses the position in the SVG file as default. The top-left corner of the page is the top-left corner of the lasercutter. This is a useful feature if you want to cut something that doesn't start at the corner, and also quite intuitive as long as the SVG page size matches the lasercutter print bed size.

What's your suggestion regarding this use-case?

@t-oster
Copy link
Owner

t-oster commented Jan 1, 2020

If this feature is really wanted, it should maybe be tied to the lasercutter origin setting like #549

@mgmax
Copy link
Collaborator

mgmax commented Aug 16, 2020

Closing due to lack of response -- It's not clear what the intended solution should be. With the current suggestion, we would no longer have "position on SVG page = position on VisiCut page", which would break some use cases.

@mgmax mgmax closed this as completed Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants