#emc-devel | Logs for 2010-08-07

[14:07:58] <micges> in 2.4 branch: right click on Axis gcode preview allow to send run command even in estop state, this patch fix it: http://pastebin.com/2UDL4sv7
[14:27:25] <jepler> micges: please push
[14:29:45] <jepler> well actually .. won't that change it from showing an error message to silently doing nothing?
[14:30:28] <jepler> the option will still appear in the menu, but choosing it will do nothing
[14:33:10] <SWPadnos> that kind of opens up a fundamental question: to what extent should the user interface pretend that EMC2 doesn't really have different modes of operation?
[14:33:40] <SWPadnos> AXIS hides some stuff by automatically switching between auto/manual/MDI
[14:34:04] <SWPadnos> should the "machine on/machine off" thing be hidden as well?
[14:34:16] <SWPadnos> (personally, I don't think so)
[14:37:14] <micges> second attempt: http://pastebin.com/pYui2Lnn
[14:37:32] <micges> run from here is grayed when emc is disabled
[14:37:51] <jepler> http://emergent.unpy.net/files/sandbox/0001-grey-out-run-from-here-when-running-is-sure-to-fail.patch
[14:38:12] <jepler> well micges wins for writing simpler code
[14:38:22] <SWPadnos> heh
[14:38:35] <jepler> I think the first change (of select_run_from) becomes unneeded when the second change (grey out menu entry) is made.
[14:38:38] <SWPadnos> if you gray out the menu item, do you still need to protect the execute call?
[14:38:47] <micges> no
[14:39:59] <micges> yes it works
[14:41:55] <jepler> then push just the change
[14:41:56] <jepler> + if not manual_ok():
[14:41:56] <jepler> + rmenu.entryconfigure(2, state = 'disabled')
[14:42:18] <micges> yes I'm doing it
[14:42:27] <jepler> thanks
[14:42:34] <jepler> * jepler is off to find some breakfast (and coffee)
[14:43:00] <CIA-2> EMC: 03micges 07v2.4_branch * r51aeaaaf830e 10/src/emc/usr_intf/axis/scripts/axis.py: axis: gray out 'run from here' on right click menu when emc is not enabled
[14:57:46] <micges> jepler: I've untracked file in 2.4 : #docs/man/man9/bldc_hall3.9
[14:58:08] <micges> but I've added it to gitcore in master
[14:58:55] <micges> but I've added it to .gitignore in master
[14:59:39] <micges> if I fix it in 2.4 does it makes any conflict when merging 2.4 to master?
[15:34:30] <jepler> micges: it will probably be an easy conflict to resolve.
[15:56:35] <CIA-2> EMC: 03micges 07v2.4_branch * rbf0cccc8078c 10/docs/man/man9/.gitignore: add bldc_hall3.9 to .gitignore
[17:45:52] <IchGuckLive> hi how is the status to G12-G13
[17:46:15] <IchGuckLive> im on 2.4.3 it says error G word
[18:16:19] <cradek> no idea what g12-g13 is
[18:20:34] <cradek> not in my fanuc 10 manual
[19:18:09] <jepler> somebody wrote this on the wiki: http://wiki.linuxcnc.org/emcinfo.pl?G12-13 suggesting it's from haas. It's not implemented in any version of emc2, though.
[19:37:18] <cradek> G12/G13 subunits are alpha units of heterotrimeric G proteins that regulate cell processes through the use of guanine nucleotide exchange factors.
[19:49:30] <skunkworks> that doesn't seem right
[19:49:34] <skunkworks> ;)
[19:49:47] <cradek> yeah, I bet jeff's was right
[20:06:13] <alex_joni> the Fanuc 16i/160i/160is-MB manual I have says G12.1 and G13.2 are Polar coordinate interpolation mode
[20:08:37] <alex_joni> same for Fanuc 21i/210i, but there besides G12.1 you can use G112 and G113 for G13.1
[20:38:40] <alex_joni> lol, the last message on the rtai mailing list is hilarious
[20:39:11] <alex_joni> https://mail.rtai.org/pipermail/rtai/2010-August/023530.html
[20:46:38] <mozmck> I see the image name for the last liveCD was "emc2buntu8.04"
[20:46:59] <mozmck> I was planning on "LinuxCNC Live-CD", but maybe I should have 10.04 in there somewhere?
[20:47:30] <cradek> where is it shown?
[20:48:01] <mozmck> I think it is shown as the disk name.
[20:48:58] <mozmck> on the desktop icon, in nautilus, etc.
[20:49:09] <cradek> oh ok, I've seen that
[20:49:24] <cradek> what do you think is best?
[21:00:22] <mozmck> I don't know. maybe "Emc2-LinuxCNC10.04"?
[21:06:59] <cradek> that looks good to me
[21:41:42] <alex_joni> mozmck: maybe make it emc2 instead of Emc2
[21:48:07] <mozmck> alex_joni: an initial capital letter looks better imo - maybe EMC2 instead?
[21:49:13] <cradek> I agree since in general, capitals for acronyms are the custom
[21:54:56] <SWPadnos> emc2-2.4.3 + Ubuntu 10.04 ?
[21:55:20] <SWPadnos> (as the title, so you can see which EMC version you have as well
[21:56:32] <alex_joni> there's a max length iirc
[21:58:32] <SWPadnos> 16 chars it seems
[21:59:01] <alex_joni> Ubuntu10.04+emc2
[21:59:28] <SWPadnos> I don't know if 16 chars includes a terminating NULL :)
[22:00:04] <SWPadnos> emc2.4.3+10.04
[22:00:05] <cradek> the exact spelling of this string is among the least important things I can imagine
[22:00:11] <SWPadnos> emacs!
[22:00:13] <SWPadnos> oops
[22:00:38] <cradek> 2.4.3+10.04 = 12.44.3?
[22:00:50] <SWPadnos> 12.8.3
[22:00:55] <alex_joni> 2.14.7
[22:01:07] <SWPadnos> or 210.404.3
[22:01:18] <alex_joni> 404 not found
[22:01:21] <SWPadnos> or 2.4.310.04
[22:02:54] <alex_joni> InfraRecorder has no issue with creating a 30-char title for a new disk
[22:02:58] <SWPadnos> that or put a short file named "This is EMC2 version 2.4.3 on Ubuntu 10.04+RTAI extensions"
[22:03:16] <alex_joni> there is a file with a description
[22:03:17] <SWPadnos> Joliet allows more, and should be OK on any semi-modern-esque machine