Back
[12:36:49] <andypugh> Halshow LED colours. It’s a simple change, but I would like to have a few other opinions about the advisability.
[12:37:48] <andypugh> Currently it is “Firebrick4” for false and “Yellow” for true. I wonder if originally it was “firebrick4” and “bright red” so it looked a bit like a red LED?
[13:38:19] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15Petross404 opened issue #226: Linuxcnc configuration failes if python2.7 is not default in Gentoo->error: Python version too old (2.7 or newer required) 02
https://github.com/LinuxCNC/linuxcnc/issues/226
[13:47:42] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/external_offsets ad0481c 06linuxcnc 10(17 files in 7 dirs) external axis-offset hal pins (v13) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ad0481c
[13:47:42] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/external_offsets 0c43d79 06linuxcnc 10src/emc/motion/command.c command.c test fix for Precise-amd64 failures * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=0c43d79
[13:53:25] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/external_offsets 51bf488 06linuxcnc 10src/emc/motion/command.c command.c test fix for Precise-amd64 failures (3) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=51bf488
[16:26:39] <KimK_laptop> andypugh: I seem to recall there's a standard (European?) for LEDs where in brief, Red for things that are *not* supposed to light up (failures,etc.), Green for things that *are* supposed to light up, and Yellow for things that are other than Green/Red, or can't tell, or don't know. So since *everything* in Halshow is "don't know", I would vote Bright Yellow for on, with off as Dark Yellow (Brown?) or some Dark Grey.
[16:27:11] <andypugh> Yes, there is, but that is irrelevant here
[16:27:29] <linuxcnc-build_> build #2316 of 4016.deb-wheezy-i386 is complete: Failure [4failed shell_1] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4016.deb-wheezy-i386/builds/2316 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[16:27:48] <KimK_laptop> andypugh: I think I would find Black for off as distracting, as if the LED was missing, leaving a hole in the panel.
[16:27:48] <linuxcnc-build_> build #716 of 4017.5.deb-wheezy-armhf is complete: Failure [4failed shell_1] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/4017.5.deb-wheezy-armhf/builds/716 blamelist: dummy, Dewey Garrett <dgarrett@panix.com>
[16:28:04] <andypugh> I guess we could simply swap the current “red for false” to “grey for false” and keep the yellow
[16:28:48] <KimK_laptop> Sounds good, and that's only one change.
[16:29:10] <andypugh> You need to consider the sitiuation where all the LEDs are the same colour, and whether it seems to indicate 1 or 0.
[16:29:35] <andypugh> Someone on the forum saw 4 red LEDs and assumed “all TRUE”
[16:30:34] <KimK_laptop> If the LED is "brighter" than the surround, then I would consider it on. Which is apparently what the forum fellow did, quite reasonably.
[16:31:45] <andypugh> The reason I liked green and grey is that it immediately looks different in both states to what it is now, making it glear that there has been a change.
[16:34:23] <JT-Shop> works for me
[16:34:33] <KimK_laptop> Oh, I see, so users will notice something different and realize there has been a change? I guess that sounds good too. Might help debugging different versions too. ("Wait, he said said his LED was red, ask him if he's using the current version.")
[16:35:10] <JT-Shop> I wonder if there is any reason to offer hard drives with RTAI vs Rt Preempt
[16:37:46] <KimK_laptop> Someone is offering LinuxCNC hard drives?
[16:37:59] <JT-Shop> yea
[16:38:19] <JT-Shop> https://mesaus.com/index.php?route=product/category&path=68
[16:41:09] <KimK_laptop> I see, congratulations! RTAI might be more valuable to those running steppers on raw hardware and a parallel port breakout box.
[16:42:02] <JT-Shop> ah didn't think of that
[16:42:09] <KimK_laptop> But maybe that's not what you're trying to encourage there.
[16:42:52] <JT-Shop> I don't care how they use it I'm just offering Linux Mint configured with all the things that make life easy
[16:44:10] <KimK_laptop> Oh, excellent. Yes, I'd like to get LinuxCNC going (in realtime) on Mint18 (18.1 is out now, I hear.)
[16:45:03] <JT-Shop> working on Mint 18 now
[16:45:17] <JT-Shop> I understand there is a few bugs left to fix
[16:45:56] <KimK_laptop> Great! Just for your product line, or will you be putting out a script, or a deb, or something?
[16:46:31] <JT-Shop> actually I have debs that auto update :)
[16:46:53] <JT-Shop> working on the signing part now
[16:48:18] <KimK_laptop> Nice. I'll look forward to an announcement in the future. Thanks for working on this, please keep us informed.
[16:51:19] <KimK_laptop> Grub would allow selection of the various kernels you provide, right? So the buyer could pick-and-choose? It seems like it would.
[16:51:21] <JT-Shop> ok
[16:51:59] <JT-Shop> ah the debs are LinuxCNC built for Linux Mint versions
[16:54:57] <KimK_laptop> Grub (under Mint, also Ubuntu) eventually develops a long list of installed kernels, In the past I have had to remove some to keep the grub menu from getting too long, but newer grubs hide everything under "more choices" or similar, so that's nice.
[20:44:47] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15jepler closed issue #226: Linuxcnc configuration failes if python2.7 is not default in Gentoo->error: Python version too old (2.7 or newer required) 02
https://github.com/LinuxCNC/linuxcnc/issues/226
[21:28:16] <skunkworks_> log
[21:28:22] <skunkworks_> zlog
[22:13:26] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 6a6fbed 06linuxcnc 03lib/python/qtscreen/notify.py qtscreen -add a desktop message display library * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6a6fbed
[22:13:27] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 ad86ba9 06linuxcnc 10share/qtscreen/skins/qt_cnc/qt_cnc.ui 10share/qtscreen/skins/qt_cnc/qt_cnc_handler.py qtscreen -add status messages to test screen * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ad86ba9
[22:13:27] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 21ba0c0 06linuxcnc 10lib/python/qtvcp_widgets/graphics.py qtvcp -reset zoom distance after reloading a file. * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=21ba0c0
[22:13:29] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 4a6997f 06linuxcnc 03lib/python/qtscreen/message.py qtscreen -add a mesagee dialog system to library * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4a6997f
[22:13:33] <KGB-linuxcnc> 03Chris Morley 05qtvcp-2.7 c28e8ba 06linuxcnc 10share/qtscreen/skins/qt_cnc/qt_cnc_handler.py qtscreen -add message dialog sample to test screen * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=c28e8ba