#hazzy | Logs for 2018-08-15
Back
[00:03:44] <TurBoss> afk
[00:18:50] <Lcvette[m]> hahahahaha
[00:19:01] <Lcvette[m]> i just spent 30 inutes making one too
[00:19:16] * Lcvette[m] posted a file: robot math.docx (400KB) < https://matrix.org >
[00:25:18] * Lcvette[m] posted a file: robot math.docx (398KB) < https://matrix.org >
[00:31:48] <TurBoss> :O
[00:35:30] <TurBoss> back
[00:44:24] <TurBoss> Lcvette: you still arround?
[01:30:23] <Lcvette[m]> got sleepy
[01:30:33] <Lcvette[m]> letting in bed watching tv
[01:30:55] <Lcvette[m]> laying
[02:03:24] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson accepted merge request #1: Updated readme to reflect additional... ( https://gitlab.com )
[02:03:25] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson pushed to project branch master at Hazzy / QtPyVCP ( https://gitlab.com )
[02:03:26] -RSSBot[turbosssp:#hazzy- Hazzy activity posted a new article: Kurt Jacobson commented on merge request !1 at Hazzy / QtPyVCP ( /Hazzy/qtpyvcp/merge_requests/1#note_94604398 )
[06:11:09] -!- hazzy-lab has quit [Remote host closed the connection]
[06:33:22] -!- hazzy-lab has joined #hazzy
[06:33:22] -!- mode/#hazzy [+o hazzy-lab] by ChanServ
[06:57:57] -!- tommylight has quit [Ping timeout: 252 seconds]
[08:22:14] * hazzy-lab is headed up to NC
[08:22:21] <hazzy-lab> should be back this afternoon
[08:22:32] <hazzy-lab> morning
[08:22:54] <TurBoss> morning
[08:59:49] <jschi[m]> morning
[10:24:12] <Lcvette[m]> morning
[10:24:27] <Lcvette[m]> hazzy you ocming to visit me?
[10:46:32] <Lcvette[m]> hazzy-lab: where in NC you headed?
[11:34:09] * Lcvette[m] uploaded an image: image.png (222KB) < https://matrix.org >
[12:04:41] <jschi[m]> +1 - looking good
[12:24:41] <Lcvette[m]> hey Jeff!
[12:24:56] <Lcvette[m]> thanks, just sent that to a friend
[12:25:13] <Lcvette[m]> i don't use a haimer and he does so im trying to get some input on that process
[12:25:21] <Lcvette[m]> i know many folks love their haimers
[12:25:29] <Lcvette[m]> he made some good points
[12:25:43] <Lcvette[m]> need to find a way to define the haimer tool similar to the probe
[12:26:07] <Lcvette[m]> thinking we need to develop a master tool mode like MSM has some how
[12:44:59] <jschi[m]> I use a haimer - don't have a probe connected (yet) - I usually just zero in on X, Y, Z with the haimer, manually jogging to zero on the haimer dial and then zero that work offset in LCNC
[12:52:37] <Lcvette[m]> so that image above does that feel intuitive to you?
[12:55:37] <jschi[m]> not sure showing a probe makes sense if you're using a haimer or even an edge finder - simply displaying the offsets and the ability to zero - but I may be missing something
[12:57:06] <Lcvette[m]> the probe is for tool setting
[12:57:12] <Lcvette[m]> tool probe
[12:57:23] <jschi[m]> I typically use my MPG to jog but having an on screen jog control might be necessary - ah yes tool probe
[12:57:24] <Lcvette[m]> that is for setting the probe offset location on the table
[12:57:34] <jschi[m]> i see
[12:57:43] <jschi[m]> like I said - missing some context
[12:57:48] <Lcvette[m]> defining it if you have one, if not it would be ignored
[12:58:05] <jschi[m]> k, that makes sense
[12:59:02] <Lcvette[m]> however if you have never used one, you are missing out
[12:59:09] <Lcvette[m]> same goes for a touch probe
[12:59:54] <Lcvette[m]> we will have to get you setup with one
[13:00:09] <Lcvette[m]> your haimer will collect dust after that..lol
[13:02:14] <jschi[m]> I have a touch probe - just haven't wired it in - TBH was thrilled to get my machine running. New shop setup will be better for tweaking LCNC
[13:02:40] <Lcvette[m]> oh yeah
[13:02:49] <Lcvette[m]> i call that the stages of cnc
[13:04:17] <Lcvette[m]> thats good it gives me a good idea of where your head space is
[13:04:18] <Lcvette[m]> do you use cnc outside of your G0704? for work or?
[13:07:14] <jschi[m]> just the G0704 for now - been gearing up to support my knife making - it's been a good learning experience - have my eyes open for a bigger mill and always looking for a lathe.
[13:07:22] <jschi[m]> My current side project is automating my surface grinder
[13:07:25] <jschi[m]> though not CNC
[13:08:37] <Lcvette[m]> nice!
[13:08:59] <Lcvette[m]> ok very good, so you will likely have many questions on things along the way through here
[13:09:35] <Lcvette[m]> thats good, don't stay quiet, be sure to speak up so I can guide you through whats going on for better understanding ont he work flow and feel of the gui
[13:10:02] <jschi[m]> awesome
[13:10:45] <Lcvette[m]> if you have the probe sim running did you get a chance to play with it?
[13:11:46] <jschi[m]> not much - I just ran the master branch which doesn't look a whole lot like your screenshots
[13:11:59] <Lcvette[m]> lol.. yeah
[13:12:06] <Lcvette[m]> thats what i started from
[13:12:25] <Lcvette[m]> i just started dabbling a bit and it turned into this
[13:13:24] <Lcvette[m]> i actually had never seen or done anything with code until about 4 weeks ago
[13:13:40] <jschi[m]> nice
[13:13:48] <Lcvette[m]> some im literally learning on the go
[13:14:03] <Lcvette[m]> thats why its taking me forever to dothings
[13:14:30] <jschi[m]> all good - there are multiple curves here - LCNC is nothing but curves then QT, etc etc
[13:15:26] <Lcvette[m]> never used linux anyhting until may and not seriously really until june
[13:15:41] <Lcvette[m]> so its a crash course in everything
[13:16:24] <Lcvette[m]> been a mach3 user for the lst 10 years
[13:17:03] <Lcvette[m]> i have a really cheap keyboard that fights me so excuse the multiple sp and typo errors
[13:17:04] <Lcvette[m]> lol
[13:58:08] <Lcvette[m]> im not having a good time making a simple table
[13:58:25] <Lcvette[m]> for some reason the headers want to turn themselves off
[13:58:27] <Lcvette[m]> any thoughts?
[14:03:41] * Lcvette[m] uploaded an image: image.png (272KB) < https://matrix.org >
[14:04:09] <Lcvette[m]> everything looks correct here, header display options are checked
[14:04:15] <Lcvette[m]> i save it like this
[14:05:09] * Lcvette[m] uploaded an image: image.png (222KB) < https://matrix.org >
[14:05:18] <Lcvette[m]> when i open it this is what i get
[14:05:41] <Lcvette[m]> then when i go back into the qt designer, thisd is what i have
[14:05:46] -HaikuBot[m]:#hazzy- then when i go back
[14:05:47] -HaikuBot[m]:#hazzy- into the qt designer,
[14:05:47] -HaikuBot[m]:#hazzy- thisd is what i have
[14:06:20] * Lcvette[m] uploaded an image: image.png (261KB) < https://matrix.org >
[14:06:42] <Lcvette[m]> the display headers check boxes maghically turned themselves off
[14:07:11] <Lcvette[m]> ive looked online for a solution but have not found anyone with this problem
[14:07:16] <Lcvette[m]> im stumped
[14:07:32] <Lcvette[m]> thought this would be a fairly simple leg of the build today
[14:07:33] <Lcvette[m]> lol
[14:07:39] <Lcvette[m]> thats whatb i get for thinkin
[14:08:36] <jschi[m]> 😅
[14:11:05] <Lcvette[m]> i'm tellin ya
[14:11:14] <Lcvette[m]> somethings are just a pain
[14:17:48] * Lcvette[m] uploaded an image: image.png (233KB) < https://matrix.org >
[14:18:04] <Lcvette[m]> 2 hours i screwed with it
[14:18:15] <Lcvette[m]> hit the little nuke button the red arrow and it fixed it
[14:18:30] <Lcvette[m]> apparantly it likes the default state rather then the selected state
[15:15:27] * Lcvette[m] uploaded an image: image.png (241KB) < https://matrix.org >
[15:28:31] * Lcvette[m] uploaded an image: image.png (241KB) < https://matrix.org >
[15:39:51] * Lcvette[m] uploaded an image: image.png (240KB) < https://matrix.org >
[15:46:01] * Lcvette[m] uploaded an image: image.png (240KB) < https://matrix.org >
[15:46:24] <Lcvette[m]> ok, sorry loits of small tweaks to the size were needed i kept missing
[15:46:24] <Lcvette[m]> thoughts?
[15:47:00] <Lcvette[m]> ptryy basic as a table i guess
[16:03:25] <Lcvette[m]> pushed changes!
[16:04:59] * Lcvette[m] uploaded an image: image.png (240KB) < https://matrix.org >
[16:18:52] -!- hazzy-lab has quit [Remote host closed the connection]
[16:25:42] -!- hazzy-lab has joined #hazzy
[16:25:42] -!- mode/#hazzy [+o hazzy-lab] by ChanServ
[17:10:47] <Lcvette[m]> boy its quiet in here today
[17:56:43] <TurBoss> hello
[17:56:54] <TurBoss> noise noise !!!!
[17:56:56] <Lcvette[m]> Hurray!!
[17:57:03] <Lcvette[m]> lol
[17:57:12] <TurBoss> :p
[17:57:18] <TurBoss> i'm here to ask
[17:57:19] <Lcvette[m]> xD
[17:57:22] <TurBoss> lol
[17:58:08] <TurBoss> could you give me algorithm based on a given robot geometry
[17:58:13] <Lcvette[m]> did you math it out?
[17:58:15] <TurBoss> lol
[17:58:29] <TurBoss> im working on it with my friend
[17:59:05] <TurBoss> could you give me at least some points
[17:59:39] <Lcvette[m]> oh man
[17:59:46] <Lcvette[m]> your asking me?
[17:59:48] <Lcvette[m]> your in trouble
[17:59:51] <Lcvette[m]> lol
[18:00:14] <Lcvette[m]> im not versed in the ways of robots
[18:00:15] <TurBoss> hehehe
[18:00:19] <TurBoss> ok ty
[18:00:25] <TurBoss> no worries
[18:00:37] <TurBoss> kcj is away?
[18:00:52] <Lcvette[m]> he is here in North CArolina somewhere he said
[18:00:55] <TurBoss> oki
[18:01:08] <Lcvette[m]> what movements do you need?
[18:01:36] <TurBoss> i want to get the workspace
[18:01:50] <TurBoss> i have ik
[18:02:01] <Lcvette[m]> show me what you have
[18:02:08] <Lcvette[m]> i may be able to help
[18:02:15] <Lcvette[m]> is it the same thing from last night?
[18:02:21] <TurBoss> no
[18:02:25] <TurBoss> sek
[18:03:09] <TurBoss> the problem realy is the mechinical limits :(
[18:03:26] <Lcvette[m]> meaning?
[18:03:40] <Lcvette[m]> joint lengths?
[18:03:51] <Lcvette[m]> or actual limitations of the mechanics
[18:03:57] <TurBoss> gear physically hiting the joints
[18:03:59] <TurBoss> lol
[18:04:12] <TurBoss> i want to determine the worl area
[18:04:24] <Lcvette[m]> world
[18:04:29] <TurBoss> we are working with matlab
[18:04:33] <TurBoss> work
[18:04:36] <TurBoss> ***
[18:04:45] <TurBoss> work area sorry
[18:04:51] <Lcvette[m]> ok
[18:04:57] <Lcvette[m]> spins 360?
[18:05:17] <TurBoss> in x yes
[18:05:26] <TurBoss> in z and y no
[18:05:31] <Lcvette[m]> have an axis diagram?
[18:05:37] <TurBoss> yes
[18:05:42] <Lcvette[m]> right i meant on the base
[18:05:51] <Lcvette[m]> revolves
[18:06:09] <Lcvette[m]> so we are looking for a cross sectional area
[18:06:21] <Lcvette[m]> in 2d space
[18:06:30] <Lcvette[m]> which will then be revolved
[18:06:36] <Lcvette[m]> to give the work volume
[18:07:02] <TurBoss> currently having abreak
[18:07:11] <TurBoss> ill send you a vid
[18:07:16] <Lcvette[m]> ok
[18:07:21] <TurBoss> ty
[18:08:30] <Lcvette[m]> it will look similar to the circles drawing in that document
[18:09:27] <Lcvette[m]> ?
[18:12:20] <TurBoss> not much
[18:12:52] * TurBoss uploaded a video: file1534371145330.mp4 < https://matrix.org >
[18:14:42] <TurBoss> lol
[18:17:13] <Lcvette[m]> that looks like a problem
[18:18:24] <Lcvette[m]> you need to buy some harmonic drive units
[18:18:34] <Lcvette[m]> or make some
[18:18:51] <Lcvette[m]> much better for robots
[18:20:18] <TurBoss> ok
[18:20:31] <TurBoss> i'm total newbie
[18:20:34] <TurBoss> hehehe
[18:21:21] <TurBoss> no worries i'll do by softeare
[18:21:43] <Lcvette[m]> https://www.youtube.com
[18:23:23] <TurBoss> ohhh
[18:24:52] <Lcvette[m]> then motors are all in regular rotation ratio's
[18:24:58] <Lcvette[m]> not arm throw ratio
[18:25:01] <Lcvette[m]> much easier
[18:26:32] <Lcvette[m]> x(motor rotation) = axis rotation in degrees
[20:33:32] <Lcvette[m]> hazzy-lab: you back yet?
[20:36:36] <Lcvette[m]> turboss or jeff
[20:37:27] <hazzy-dev> yes
[20:37:34] <hazzy-dev> I have to run
[20:37:46] <hazzy-dev> be back for good a a bit
[20:37:46] <Lcvette[m]> lol
[20:37:56] <Lcvette[m]> ok
[20:44:03] <jschi[m]> I'm just showing up - looking through the ppclone branch and getting it running, taking some notes & questions
[20:44:59] <Lcvette[m]> your able to get it now?
[20:45:03] <Lcvette[m]> awesome!!\
[20:45:30] <jschi[m]> yeah, looks like either the fonts are missing for me or I'm at a jacked up resolution
[20:45:44] <Lcvette[m]> ah!!
[20:45:53] <Lcvette[m]> sek
[20:46:46] * jschi[m] uploaded an image: Screen Shot 2018-08-15 at 8.45.37 PM.png (764KB) < https://matrix.org >
[20:46:56] <Lcvette[m]>
[20:46:56] <Lcvette[m]> lemme know when your ready
[20:46:58] <Lcvette[m]> you will need a terminal
[20:47:11] <jschi[m]> ready
[20:48:01] <Lcvette[m]> well, hold on a sec
[20:48:08] <Lcvette[m]> lost someof my notes
[20:49:13] <jschi[m]> all good - am trying to add stuff to my notes here and update readme/automate some of the setup stuff (for the next soul)
[20:51:18] <jschi[m]> so first simple UI thing I was thinking about - in the 'steps' for the jog interface - we show four buttons, but `INCREMENTS` in the .ini file support an arbitrary list
[20:51:46] <jschi[m]> so are we going to limit to four? or ?? I'll have to see what gmoccapy/axis do with that
[20:52:01] <Lcvette[m]> 4?
[20:52:13] <Lcvette[m]> increments
[20:52:45] <Lcvette[m]> once you get used to runing your machine you will likely use no more than 2\
[20:52:48] <Lcvette[m]> 2
[20:52:49] <jschi[m]> yes, the screens show .0001, .001, 010, .100
[20:52:50] <jschi[m]> right
[20:53:23] <jschi[m]> so my question is we need to code/connect reading those increments from the .ini file and display those values on the screen -
[20:53:29] <Lcvette[m]> you have a real mpg?
[20:53:58] <Lcvette[m]> yes
[20:53:59] <jschi[m]> yes, but use the increments on the screen occasionaly (touch screen) gmoccapy
[20:54:15] <Lcvette[m]> hazzy knows all the connections to lcnc
[20:54:30] <Lcvette[m]> im just the screen guy
[20:54:31] <Lcvette[m]> lol
[20:54:37] <Lcvette[m]> for now at least
[20:54:40] <jschi[m]> my point is that we can't hardcode 0.0001, etc in the UI - so we'll need to limit/ignore after 4 entries
[20:55:34] <jschi[m]> right, I was going to chat @ hazzy tonight to see where I can dig in - seems like backing up some of the UI with real wiring to the config files/lcnc stuff would be good
[20:56:40] <Lcvette[m]> im not sure i understand about the hardcode
[20:56:42] <jschi[m]> will chat at him if/when he comes online - I'm around for a bit - I'm on the 4:30am wakeup these days so late night ...
[20:57:07] <jschi[m]> we've drawn those 4 step sizes - in lcnc they come out of the ini file
[20:57:09] -HaikuBot[m]:#hazzy- we've drawn those 4 step
[20:57:10] -HaikuBot[m]:#hazzy- sizes - in lcnc they come out
[20:57:11] -HaikuBot[m]:#hazzy- of the ini file
[20:57:15] <Lcvette[m]> you mean because lcnc has 6 possible for the increments?
[20:57:29] <jschi[m]> I would expect that we'd read those values and display them on the step buttons
[20:57:54] <jschi[m]> yeah, I'm ok with limiting to four but also someone (metric) may have different step sizes
[20:57:54] <Lcvette[m]> right, the ini would just be written with the increments listed
[20:57:54] <jschi[m]> 0.02
[20:57:59] <jschi[m]> yes
[20:58:31] <Lcvette[m]> for metric, i think we will need to do some magic
[20:59:01] <Lcvette[m]> maybe have the text in the qpushbuttons be set from the ini
[20:59:18] <jschi[m]> so I'm asking for two reasons - one - does it make sense to wire those up (if they aren't already) and 2.) are we forcing hard choices like limiting to four - adding a scroller or other to support arbitrary complexity doesn't yield good UI
[20:59:25] <Lcvette[m]> same for several of the "inch" that will need to turn to "mm" etc
[20:59:38] <jschi[m]> we can get them as values and convrt to strings
[20:59:59] <Lcvette[m]> no i don't care those are just place holders
[21:00:33] <Lcvette[m]> i would prefer people choose their own flavors if its possible to have the ini set the button values
[21:00:45] <Lcvette[m]> they would as you said be limited to 4 due to screen constraints
[21:01:05] <Lcvette[m]> but they should have the ability to choose whatever those 4 should be for their needs
[21:01:27] <jschi[m]> yeah, the default measurment for increments is the `UNITS` for the machine setup - iirc you can add optional units to the INCREMENTS spec - just details
[21:01:45] <Lcvette[m]> correct
[21:02:03] <Lcvette[m]> changing units in the ini will dictate all machine units
[21:02:25] <Lcvette[m]> but youn can cherry pick items using mm or in on the end if needed in the ini
[21:02:42] <jschi[m]> I guess as we think about coding this you have some folks that will only have two entries or three entries or 10 entries in `INCREMENTS` so with that in mind we kind of need to account for that in the design
[21:03:05] <jschi[m]> all good - displaying the increment/measurement should be easy
[21:03:20] <Lcvette[m]> lcnc only has 5 or 6 if memory serves
[21:03:43] <jschi[m]> deciding on max #, layout when only two are present etc
[21:04:17] <Lcvette[m]> i doubt people would choose less than is available
[21:04:31] <Lcvette[m]> i guess i could be wrong
[21:05:09] <Lcvette[m]> but i would say limit it to 4 if they choose fewer it just makes the buttons invalid
[21:05:41] <jschi[m]> or not display buttons for which there is no increment e.g. keep the buttons fixed width/spacing
[21:05:59] <Lcvette[m]> cool
[21:06:05] <Lcvette[m]> that works too
[21:06:34] <Lcvette[m]> you know how to do all that?
[21:07:21] <jschi[m]> you can't see my hand waving but yeah I can visualize what needs to happen - need to get up to speed on this codebase to actually make it happen
[21:07:37] <jschi[m]> might be a good starter project but will check with hazzy
[21:07:52] <jschi[m]> at least I can describe it in words 😀
[21:08:27] <Lcvette[m]> lol
[21:08:32] <Lcvette[m]> more than i can do
[21:08:32] <Lcvette[m]> lol
[21:10:39] <jschi[m]> I can draw stick drawings
[21:10:57] <Lcvette[m]> lol
[21:16:10] <Lcvette[m]> ok, ready for the fonts?
[21:16:41] <Lcvette[m]> go to terminal and type
[21:16:55] <Lcvette[m]>
[21:16:55] <Lcvette[m]> cd ~/.local/share/fonts/truetype
[21:17:11] <Lcvette[m]>
[21:17:11] <Lcvette[m]> if no directory, then:
[21:17:21] <Lcvette[m]>
[21:17:22] <Lcvette[m]> mkdir -p ~/.local/share/fonts/truetype
[21:17:31] <Lcvette[m]> then type
[21:18:29] <Lcvette[m]> wget https://github.com
[21:19:53] <jschi[m]> bingo!
[21:19:55] <jschi[m]> nice
[21:20:04] <Lcvette[m]> some code-fu hazzy taught me
[21:20:15] <Lcvette[m]> more better?
[21:20:26] <jschi[m]> yeah that fixed the display sizing issue
[21:20:36] <Lcvette[m]> the latest version of the interface is mine the probe_basic_1920
[21:20:44] <jschi[m]> will add a task to check for font or at least report it missing
[21:21:06] <Lcvette[m]> is there a way to bundle it?
[21:21:19] <jschi[m]> I'm sure - just don't know that one yet
[21:21:32] <Lcvette[m]> this will sound silly, but like "pack-n-go"
[21:21:52] <Lcvette[m]> i know design software, cad, cam etc
[21:22:18] <Lcvette[m]> they usually have that feature where it bundle all dependents up that are needed
[21:23:01] <jschi[m]> yeah, it's common to have dependencies, some bundled some not - I'm just not hip as how to do that on linux apps - ask me about iOS, android or web apps and I have you covered ;-0
[21:23:16] <Lcvette[m]> hahahaha
[21:23:18] <Lcvette[m]> nice
[21:23:27] <Lcvette[m]> we'll have to remind hazzy
[21:23:56] <Lcvette[m]> at least to add it to the notes section on how to get the fonts
[21:25:09] <jschi[m]> all good, added it to my notes - I updated the readme last night, can continue to do so
[21:25:22] <Lcvette[m]> sweet!
[21:28:22] -HaikuBot[m]:#hazzy- so yeah I need to
[21:28:22] <jschi[m]> so yeah I need to get synced up on the branch that has probe_basic_1920
[21:28:23] -HaikuBot[m]:#hazzy- get synced up on the branch that
[21:28:23] -HaikuBot[m]:#hazzy- has probe_basic_1920
[21:29:02] <Lcvette[m]> its current
[21:29:16] <Lcvette[m]> do you know how to do it?
[21:29:54] <jschi[m]> I don't see it in hazzy's repo so I'm assuming it's in yours?
[21:30:07] <Lcvette[m]> yes
[21:30:09] <jschi[m]> and folks are pulling from it
[21:30:10] <jschi[m]> k
[21:30:13] <jschi[m]> yeah I can do that
[21:30:23] <Lcvette[m]> i suppose they are
[21:30:36] <Lcvette[m]> i don't know i just know how to send my work there
[21:30:47] <Lcvette[m]> hahaha
[21:30:57] <Lcvette[m]> just a bumbling worker ant
[21:43:16] <hazzy-lab> hey all, back for a few minutes
[21:43:24] <hazzy-lab> sorry for being in and out so much
[21:43:34] <hazzy-lab> actually, being in so little :D
[21:43:51] <jschi[m]> all good, pleasure to meet you
[21:44:09] <hazzy-lab> great to meet you too!
[21:44:14] <hazzy-lab> thanks for the PR
[21:44:30] <Lcvette[m]> Hurray!
[21:44:36] <Lcvette[m]> fearless leader has returned
[21:44:42] <jschi[m]> was chatting at lcvette about 'steps' on ui, see above for debate etc - wondering what area I can dig into - was thinking about wiring up .ini `INCREMENTS` to Ui steps
[21:44:53] <jschi[m]> as small step for mankind and to get my feet wet
[21:45:12] <jschi[m]> I'm happy to work on whatever just need a bit of guidance/push on where to focus
[21:45:17] <hazzy-lab> that is an excellent place to start!
[21:45:52] <hazzy-lab> let me explain how things work
[21:47:46] <jschi[m]> cool
[21:48:53] <hazzy-lab> basically the goal of QtPyVCP is to be toolkit for building virtual control panels (VCPs) so custom widgets should generally be based on a single QtWidget if possible, and be as flexible as possible
[21:50:52] <hazzy-lab> if an individual VCP need a customized which is not likely to be useful else were then it should be put in the VCP dir, rather than with the main QtPyVCP widget
[21:52:34] <jschi[m]> ok, I'll take baby steps - so I'll look over that divison in the current code base - there are a few branches going - I'm on ppclone currently - any better place to derive from to start?
[21:54:35] <hazzy-lab> ppclone is fine, it will eventually be merge back to master
[21:55:15] <hazzy-lab> the jog increments buttons you mention are obviously a standard widget, so should go in the widgets/input_widgets dir
[21:55:38] * Lcvette[m] uploaded an image: image.png (139KB) < https://matrix.org >
[21:56:02] <Lcvette[m]> load meters?
[21:56:50] <hazzy-lab> Lcvette[m]: Nice!!
[21:57:08] <Lcvette[m]> can they work as load meters?
[21:57:25] <jschi[m]> sounds good - still getting my dev environment setup - having to run vbox on my mac atm - evaluating my options
[21:57:32] <hazzy-lab> jschi[m]: There is a already a method in utilities/info.py to get the jog increment list from the INI: https://gitlab.com
[21:58:36] <jschi[m]> cool - I think I stumbled across that and that's what got me thinking about the display, max number, what happens when someone only enters two, metric etc
[21:58:54] <jschi[m]> kk, will advise - may take me a few to get rolling on this - excited
[21:59:10] <Lcvette[m]> me too!!!
[21:59:59] <hazzy-lab> hmm, doesn't look like that method gets the units for the jog increments ... Might need to work on that
[22:00:09] <hazzy-lab> (I stole it from Gmoccapy :D )
[22:00:33] <hazzy-lab> I think, or maybe touchy
[22:01:45] <Lcvette[m]> yo!
[22:02:17] <Lcvette[m]> do you think that a slider connected to a box like that can work as a load meter?
[22:02:19] <jschi[m]> will look at that
[22:02:39] <hazzy-lab> Lcvette[m]: yes, those could work as load meters!
[22:03:07] <Lcvette[m]> if we feed the data to the box it reflect to the slider movement
[22:03:22] <hazzy-lab> could probably do something with a progress bar as well, it might be better since a load meter does not need user input
[22:03:41] <Lcvette[m]> progress bar is locked at 100%
[22:03:48] <Lcvette[m]> i tried using that first
[22:04:14] <Lcvette[m]> you can change the max and min but the 100% alway seems to stay the standard
[22:04:16] -HaikuBot[m]:#hazzy- you can change the max
[22:04:17] -HaikuBot[m]:#hazzy- and min but the 100% alway seems
[22:04:18] -HaikuBot[m]:#hazzy- to stay the standard
[22:04:21] <Lcvette[m]> i didn't know how to change that so went to this
[22:05:32] * Lcvette[m] uploaded an image: image.png (3KB) < https://matrix.org >
[22:06:52] * hazzy-m uploaded an image: progress.gif (27KB) < https://matrix.org >
[22:07:17] <Lcvette[m]> spindle load often goes well over 100%
[22:07:26] <Lcvette[m]> it usually has a range of 200%
[22:07:36] <hazzy-m> aha!
[22:07:40] <hazzy-m> true :D
[22:07:53] <hazzy-lab> lol
[22:08:15] <Lcvette[m]> i didn't know how to fu the progress bar into 200%
[22:08:20] <Lcvette[m]> my fu failed me
[22:08:57] <Lcvette[m]> can we just lockout user input in the box?
[22:09:05] <Lcvette[m]> or can you fu the progress bar?
[22:09:40] <hazzy-lab> I set the max value to 250, but did not realize that the percentage label does not go over 100 :(
[22:09:46] <hazzy-lab> there has to be a solution
[22:10:05] <Lcvette[m]> i figured there may be
[22:10:12] <Lcvette[m]> but it required master fu
[22:10:17] <Lcvette[m]> not padwon fu
[22:11:23] * hazzy-m uploaded an image: Peek 2018-08-15 22-11.gif (22KB) < https://matrix.org >
[22:11:30] <hazzy-m> I fued it
[22:11:32] <hazzy-m> xD
[22:11:33] * Lcvette[m] uploaded an image: image.png (179KB) < https://matrix.org >
[22:11:51] <Lcvette[m]> well thats awesome! whats the fu secret?
[22:12:14] <hazzy-m> just change the format property from %p% to %v for value instread of %
[22:12:37] <Lcvette[m]> :P
[22:13:05] <hazzy-lab> I have to run
[22:13:07] <hazzy-lab> bbl
[22:13:16] <Lcvette[m]> that was my first attempt at a table by the way
[22:13:20] <Lcvette[m]> ok
[22:15:08] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[22:20:35] * Lcvette[m] sent a long message: < https://matrix.org >
[22:58:50] * Lcvette[m] sent a long message: < https://matrix.org >
[23:13:01] * Lcvette[m] sent a long message: < https://matrix.org >
[23:14:42] <hazzy-lab> whoa! Lcvette[m] is code-fuing
[23:14:44] <hazzy-lab> hurray!
[23:15:02] <Lcvette[m]> lcvette is copying and testing other peoples code
[23:15:05] <Lcvette[m]> but not having succes
[23:15:26] -HaikuBot[m]:#hazzy- im trying to make the
[23:15:26] <Lcvette[m]> im trying to make the progress bar turn colors at different values
[23:15:27] -HaikuBot[m]:#hazzy- progress bar turn colors at
[23:15:28] -HaikuBot[m]:#hazzy- different values
[23:15:36] <Lcvette[m]> any thoughts
[23:15:51] <Lcvette[m]> i found this online and was going to see if i could make heads or tails of it
[23:15:53] <hazzy-lab> hmm, let me look
[23:16:36] <Lcvette[m]> https://stackoverflow.com
[23:16:42] <Lcvette[m]> thats where i copied it from
[23:18:41] * Lcvette[m] sent a long message: < https://matrix.org >
[23:35:13] <Lcvette[m]> how about this?
[23:35:21] <Lcvette[m]> but it looks deeper than a style sheet
[23:35:23] <Lcvette[m]> :(
[23:37:01] <hazzy-lab> I think we might have to do our own painting ...
[23:37:02] <Lcvette[m]> https://stackoverflow.com
[23:37:07] <hazzy-lab> but that is not so hard
[23:38:23] * Lcvette[m] sent a long message: < https://matrix.org >
[23:38:28] <Lcvette[m]> this looks promising
[23:38:44] <Lcvette[m]> can you test?
[23:38:55] <Lcvette[m]> i don't know how to make the progress bar work
[23:38:55] <hazzy-lab> very promising!!
[23:38:56] <Lcvette[m]> :(
[23:38:59] <hazzy-lab> good find
[23:39:17] <hazzy-lab> its c++
[23:39:29] <hazzy-lab> I will convert it to python
[23:39:37] <Lcvette[m]> ok
[23:40:55] <Lcvette[m]> i like the idea of the whole bar changing colors too
[23:41:08] <Lcvette[m]> it will grab your attention better
[23:41:28] <Lcvette[m]> and won't look so rastafari on the screen
[23:41:29] <Lcvette[m]> lol