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

Rulers on Previews to check import size was correct #49

Open
ghost opened this issue Aug 17, 2014 · 4 comments
Open

Rulers on Previews to check import size was correct #49

ghost opened this issue Aug 17, 2014 · 4 comments

Comments

@ghost
Copy link

ghost commented Aug 17, 2014

I often find that when I import a SVG of unknown (or not recently used) origin that I have to make a test cut to validate whether it was a 72/90/96dpi.

Was thinking a simple 10mm grid over and ruler on X/Y edges on the preview would be quite helpful. Could also help with positioning of scrap materials for smaller cuts?

Peter

@ghost ghost changed the title Rules on Previews to check import size was correct Rulers on Previews to check import size was correct Aug 17, 2014
@SteveBaker
Copy link

Peter van der Walt wrote:

I often find that when I import a SVG of unknown (or not recently used)
origin that I have to make a test cut to validate whether it was a
72/90/96dpi.

Was thinking a simple 10mm grid over and ruler on X/Y edges on the preview
would be quite helpful.

Yes - that would be incredibly helpful.

Also, make it switchable between inches and centimeters?

Being able to zoom and pan the preview window would be useful too.

Could also help with positioning of scrap
materials for smaller cuts?

Yes, for sure!

Peter


Reply to this email directly or view it on GitHub:
#49

-- Steve

@ghost
Copy link
Author

ghost commented Aug 18, 2014

Thanks Steve glad you agree (; - being one of the bigger power users in the group

Also since my 4 machines range in size of cutting bed as 800x400, 1200x1500, 700x900 (changed in frontend/js/settings.js for each machine) it would have to adapt with that as well

@SteveBaker
Copy link

Yeah...things get more painful when you have multiple machines.

It would definitely help to have a per-machine settings file where you
could change things like the bed size.

One thing that bugs me is that if I utterly standardize on Red=cut,
Blue-etch and Orange=light-etch, then it would be nice to not have to
enter the speed/power for each color unless there is some exception to
that rule.

Doing that via the special tags in the SVG file is kinda helpful, but as
laser tubes age, you need to gradually decrease the cut speed and increase
the etch power. Going into each of a bazillion SVG files and changing
those numbers is painful...and if you have two or more machines, then it's
flat out unworkable.

So I think we need that per-machine settings file to provide default
speed/power combos - and for things like setting the bed size and such.

However, when you do that, the immediate next issue would be for people
who use different materials. So when I cut or etch cloth, I need
different setting than for plywood. That definitely complicates things.
But trying to remember what settings we use for cloth on this machine
versus that is horrendously error-prone, so it would be nice to have some
menu of materials that I could drop down...which would use a per-machine
database of materials.

-- Steve

Peter van der Walt wrote:

Thanks Steve glad you agree (; - being one of the bigger power users in
the group

Also since my 4 machines range in size of cutting bed as 800x400,
1200x1500, 700x900 (changed in frontend/js/settings.js for each machine)
it would have to adapt with that as well


Reply to this email directly or view it on GitHub:
#49 (comment)

-- Steve

@ghost
Copy link
Author

ghost commented Aug 20, 2014

I would also love a dropdown - you know how in Slic3r you open a INI file
for the MACHINE and then have dropdowns for quality/filament type: Similar
thing to that would be great!

Plus+ 1 for a settings file that lists machine specific things like default
feeds, bed size, offset etc

Peter

On Mon, Aug 18, 2014 at 3:39 PM, Steve Baker [email protected]
wrote:

Yeah...things get more painful when you have multiple machines.

It would definitely help to have a per-machine settings file where you
could change things like the bed size.

One thing that bugs me is that if I utterly standardize on Red=cut,
Blue-etch and Orange=light-etch, then it would be nice to not have to
enter the speed/power for each color unless there is some exception to
that rule.

Doing that via the special tags in the SVG file is kinda helpful, but as
laser tubes age, you need to gradually decrease the cut speed and increase
the etch power. Going into each of a bazillion SVG files and changing
those numbers is painful...and if you have two or more machines, then it's
flat out unworkable.

So I think we need that per-machine settings file to provide default
speed/power combos - and for things like setting the bed size and such.

However, when you do that, the immediate next issue would be for people
who use different materials. So when I cut or etch cloth, I need
different setting than for plywood. That definitely complicates things.
But trying to remember what settings we use for cloth on this machine
versus that is horrendously error-prone, so it would be nice to have some
menu of materials that I could drop down...which would use a per-machine
database of materials.

-- Steve

Peter van der Walt wrote:

Thanks Steve glad you agree (; - being one of the bigger power users in
the group

Also since my 4 machines range in size of cutting bed as 800x400,
1200x1500, 700x900 (changed in frontend/js/settings.js for each machine)
it would have to adapt with that as well


Reply to this email directly or view it on GitHub:
#49 (comment)

-- Steve


Reply to this email directly or view it on GitHub
#49 (comment).

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

1 participant