On Wednesday 01 March 2017 04:49:11 andy pugh wrote: > On 1 March 2017 at 04:32, Gene Heskett <ghesk...@shentel.net> wrote: > > Are you saying the html docs on the wiki are more up to date? > > The Wiki and the HTML docs are completely separate things. > > The HTML docs get updated every time the code gets changed, they are > 100% up to date. > > Go to www.linuxcnc.org and click "Documentation" on the bar under the > logo. > > Then choose the actual version of LinuxCNC that you want the docs for.
(In my best Tony the Tiger voice) Great! And in pyvcp.html, section 6.8 is exactly the display I want two of for axis, but when implemented as an hbar containing 2 of that, NOT. Read on. Needs a text label "Jog incr X" and "Jog incr Z" in place of the demo blue bar, and pins to use the up-dn buttons, and the numerical display showing the current jog per click size, as .0001,.0002,.0005,.0010,.0020,.0050,.0100,.0200 And I'll need a 2nd param pin to control the color of the background, changing from red to green dependent of the direction. When the jog wheel is in use. or change the sign with a weighted summer. TBD. 2 things so far with this idea; 1: putting two of these spinboxes in one /hbox, the space used is at least 2x whats needed horizontally, and widens the whole axis display, a lot. 2: The data pin it creates is read-only, and I need write. I don't care about read. I want to display the real data, straight out of the mux8 3. And the up-dn arrows ought to produce a pulse per increment, independent of the write-only display "this" input. And I just found the value displayed by the spinbox is read-only. Blows my whole idea into the next drainage. What I wanted was to give a mouse driven alternative to adjust the jog step size. This obviously won't do. Now, while thinking about what to display, it occurs to me that in terms of what I display as a jog per click size, could be the output of the mux8 that determines the multiplier IF I throw away one mult2 module, and change the setp's to match the same init as the output of the multiplier that determines the step size sent to that joints jog input. That saves one mult2 out of the code for each joint and I'd get a direct, in inches reading at the same time. Thats worthwhile. And it should still work even if your [JOINT_n[SCALE is in mm's. Anyway, that "spinbox", unless additions to the code to separate the spinners from the display can be done, and the 3" wide per spinbox can be pulled in for just the needed room for the displayed number, and the spin arrows, that 2.5" of whitespace between them is downright ugly. Progress?, damnifiknow ;-) Keeps me out of the bars. ;-) Comments welcomed. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
