#emc-devel | Logs for 2008-02-06

[09:48:48] <CIA-22> EMC: 03cmorley 07cl_v7124_branch * 10emc2/src/hal/classicladder/ (calc.c calc.h module_hal.c): fix to refresh at period rate. Unless period is less then 1 ms
[10:12:50] <CIA-22> EMC: 03cmorley 07cl_v7124_branch * 10emc2/src/hal/classicladder/edit.c: change to callfunction to display HAL signal names
[10:15:25] <CIA-22> EMC: 03cmorley 07cl_v7124_branch * 10emc2/src/hal/classicladder/Submakefile: added emc_mods.c to compile list
[11:26:12] <CIA-22> EMC: 03cmorley 07cl_v7124_branch * 10emc2/src/hal/classicladder/projects_examples/example.clp: update files-still some old ones
[11:26:17] <CIA-22> EMC: 03cmorley 07cl_v7124_branch * 10emc2/src/hal/classicladder/ (17 files): update files-still some old ones
[14:12:11] <CIA-22> EMC: 03jepler 07TRUNK * 10emc2/src/hal/user_comps/hal_input.py:
[14:12:11] <CIA-22> EMC: fix 'ZeroDivisionError' at hal_input startup when the kernel reports the same
[14:12:11] <CIA-22> EMC: value for the -min and -max of an axis
[14:13:30] <SWPadnos> weird. it doesn't look like that line should be able to throw any error
[14:13:57] <CIA-22> EMC: 03jepler 07v2_2_branch * 10emc2/debian/changelog: from TRUNK: fix ZeroDivisionError
[14:13:59] <CIA-22> EMC: 03jepler 07v2_2_branch * 10emc2/src/hal/user_comps/hal_input.py: from TRUNK: fix ZeroDivisionError
[14:16:16] <SWPadnos> oh, duh
[15:05:41] <fretless85> hey guys
[15:20:23] <jepler> SWPadnos: "or" behaves a bit strangely in Python compared to other languages
[15:21:07] <SWPadnos> no, I just hadn't read to the point where there's a division by halfrange
[15:21:27] <SWPadnos> I figured out that or means "if there's an error use the second value"
[15:21:51] <jepler> the result of 'x or y' is 'x' if bool(x) is True, otherwise the result is 'y'.
[15:22:26] <SWPadnos> ok, and an error makes bool(x) false?
[15:22:41] <SWPadnos> oh, duh
[15:22:49] <SWPadnos> maybe I should drink more coffee or something
[15:23:16] <SWPadnos> I think I should copy "oh, duh" to the lipboard, it seems I'll be using it a lot today
[15:23:23] <SWPadnos> or clipboard, whichever
[23:12:10] <alex_joni> jepler: bugreport on AXIS with emc2.2.3
[23:12:33] <alex_joni> the numpad keys only work as arrows (regardless of the Num-lock status)
[23:12:41] <alex_joni> this appears when entering g-code in MDI
[23:13:29] <alex_joni> prod me if you need more details. I'll ask :)
[23:13:33] <cradek> * cradek groans
[23:13:49] <alex_joni> cradek: ?
[23:14:34] <cradek> I think he's fixed that about seven times
[23:15:17] <alex_joni> poor jeff :)
[23:15:29] <alex_joni> I know how it feels to fix the same thing over and over again
[23:15:47] <alex_joni> * alex_joni fears the day he'll hear step & resume together with a bug report
[23:16:01] <cradek> haha
[23:16:13] <cradek> yeah you've fixed that about seven times too
[23:16:15] <alex_joni> actually I did lately, but I looked the other way :/
[23:16:20] <cradek> oh noooo
[23:16:40] <alex_joni> seems M66 doesn't work while stepping or something like that
[23:17:34] <cradek> M66 is not in my gcode quickref so it can't matter
[23:17:45] <alex_joni> heh
[23:18:00] <alex_joni> slowly I run out of fingers (of people actually running M66)
[23:19:04] <cradek> it could also be that the numpad thing has been reported seven times, but nobody filled out a bug report, so it has been forgotten seven times