ok moving right along
danfalck: the things AXIS uses to import files need not be written in Python. They can be any program that takes the input file as the commandline argument, and writes g-code to standard output.
working on some of that right now
I guess I'm just confused about the *.dxf and such as extensions
since they aren't executable files like *.py files
PROGRAM_EXTENSION = .dxf 3D Polygon Model
dxf = toolpaths.py
these two lines mean that ".dxf" will appear as a type of file to open, and that if you select "foo.dxf" then AXIS will run 'toolpaths.py foo.dxf'
you probably don't have toolpaths.py, it's some unfinished software
ok. now I get it
but I have makebore.py and boltcircle.py : )
been working on those today
makebore comes from Jon Elson's makebore.c routine, which I am nailing on a python front end
gotta go- dinner
jmkasunich: will you kick my ass if I make the doc building require Python too? I wrote a dependency-calculation program for .lyx files but it is in Python.
it won't hurt the old farm slots, because they won't have lyx available either
jepler: I happen to know he's many hours away
no, as long as you put detection of the required python in the configure script
I don't care if only 2% of people can make the docs
as long as the 2% includes the people making our packages, and as long as the build errors out cleanly for the other 98%
Executing command:ps2pdf13 '15_home_jepler_src_emc2_docs_src_hal_parport-block-diag.eps' '15_home_jepler_src_emc2_docs_src_hal_parport-block-diag.pdf'
does your system execute a different program than ps2pdf13 at this step?
I think its epstopdf
mine was also epstopdf I think
lemme run it again
I did change some things in my lyx configuration to prevent it from putting horrible jpeg artifacts in the png files it included
Executing command:epstopdf --outfile='15_home_john_emcdev_emc2head_docs_src_hal_parport-block-diag.pdf' '15_home_john_emcdev_emc2head_docs_src_hal_parport-block-diag.eps'
my png images are clean
pixelated if you blow em up to 400%, but thats to be expected, the source is fixed resolution
OK -- I'm sure you know jpeg artifacts from pixelation
I'm looking at pngs in the hal document
dunno if the ones in the user manual would be different, doubt it
I remember seeing horrible jpeg artifacts a long time ago
(like before I moved to ubuntu)
I'm 99.9% certain my lyx config here is standard
this is me not worrying about the issue anymore
does that mean you're not gonna commit hte dependency calculator?
no, I mean the issue f epstopdf vs ps2pdf13
rayh: morning ray
Hi alex. Sorry was away reading.
I just got a dapper running.
Not that I can see. I don't have the EMC stuff yet but the upgrade was painless.
is this from CD or online?
I'll be away for a couple days.
When I get back I'll install the EMC and do some tests.
CD that I burned while at a customer's shop.
But I ran it as update of packages rather than new install.
I like that.
This was on a box with Nvidia chip.
With 5 I had to hand edit the display option.
Either this read the old or correctly found the hardware and set it up.
"Because EMC2 is free software I can???t find any real help."
reply on its way
cradek, jepler: one question for you..
I want to add spindle speed override
and I need a NML message for that.. what is better in your oppinion?
extend the EMC_TRAJ_SET_SCALE ro be able to set Feed_override and spindle_speed_override ? (and maybe g0_override too?)
or leave it somehow compatible, and have new NML messages?
I suspect that adding new NML messages is better. All the old GUIs will still work, but just be unable to set the spindle speed. Otherwise, won't you break the old GUIs?
unless I fix them
but I think new messages is better too.. just increases emc.cc and .hh
as for g0 override I really don't think there's a consensus about what functionality is needed
I can see the use
FO controlling everything
and g0-fo controlling only g0
I can see the use of an overriding max vel and accel for all moves
oh.. yet another one ;)
a separate override for g0 only just seems pointless to me
cradek: not sure.. I'll work on spindle_speed_override for now
is that ok with you?
yes no problem with that
you'll probably cuss at me when you'll get at CSS
go ahead and add CSS while you're in there
I notice it's not getting done
one of these days we'll want to rewrite task
it's just insane what's in there
jepler: can you help me with something a bit later?
I have little clue about tcl/tk :/
what's the question?
it's no question.. cause it'll take you more to explain it to me than actually doing it..
I want to add a new slider to tkemc for spindle_speed_override
ah -- but that would require me to decide the best place for it on the tkemc screen, and I'm unwilling to be the one who makes that decision.
I can say where it should go :D
I'll even commit the code :)
this can also stay only in halui for now ;)