#hazzy Logs

May 13 2020

01:08 AM JamesW[m]: another day of zero new cases
01:58 AM JamesW[m]: wahho! First net new widget skeleton in Designer, laid out in a GUI, runs and getting click events trapped.
04:47 AM JamesW[m]: hazzy: for when you wake up. I'm trying to set the MDI entry line text via a signal/slot link from an item click on a list widget to the mdi entry line widget.
04:48 AM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/eQmXLkDfBveoRixCZtrUQNjt >
04:49 AM JamesW[m]: I have everything linked up ok. debug print statments fire ok as well. I have the correct decorrator as well. BUT I keep getting string errors.
04:50 AM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/bajcgxkrGGFRgLalvspjDfSy >
04:53 AM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/pTmSZlZhzFhSwGpprSaFVLAe >
04:53 AM JamesW[m]: I get this error:
04:53 AM * JamesW[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/gHpnMDGvWspyOSRQeZrjazFz >
05:01 AM JamesW[m]: ```
05:01 AM JamesW[m]: @Slot(QListWidgetItem)
05:01 AM JamesW[m]: ```
05:02 AM JamesW[m]: that's the decorating. Figured out how to get it pasted in
05:11 AM JT-Cave: roguish[m], which one, I posted two relay boards
05:26 AM JamesW[m]: $$#@##$$%%%
05:26 AM JamesW[m]: hazzy: think I cracked it. Late night probably not helping as well.
05:48 AM hazzy-m: morning
05:48 AM JamesW[m]: hi ya
05:49 AM hazzy-m: Hey!
05:49 AM hazzy-m: You got it?
05:49 AM JamesW[m]: yup
05:50 AM hazzy-m: sweet
05:54 AM JamesW[m]: https://drive.google.com/open?id=1oPgi_xIAxpuvisONUDyT3K2VfkIbG0MT
05:54 AM JamesW[m]: its pretty raw but basic mdihistory widget concept
05:55 AM JamesW[m]: linkage between the MDI entryline widget and the mdihistory widget all done via signal/slot in designer
06:13 AM JamesW[m]: already improved things a bit. keyboard arrow keys and mouse now properly drive populating the mdi entryline field. Also have new mdi entries appearing at top of history list as they are entered.
06:14 AM JamesW[m]: So first rough pass is done and functional. Will review and make sure I'm not doing redundant/silly stuff tomorrow. Then will move on to the MDIQueue_Widget
06:16 AM hazzy-m: The Germans were lazy last night, didn't answer any of my outstanding support tickets
06:16 AM hazzy-m: JamesW: that looks fantastic!
06:17 AM JamesW[m]: bummer. And cheers. Learning lots. Had a real block until I figured out I was being a dum ass and had a duplicate method name I hadn't twigged on.
06:17 AM JamesW[m]: https://github.com/joco-nz/qtpyvcp/tree/MDI-History-and-Queue-Widget
06:17 AM JamesW[m]: work in this branch.
08:52 AM Lcvette: \o.nice JamesW
08:52 AM Lcvette: * \o/ nice JamesW
08:52 AM Lcvette: morning!
10:04 AM hazzy-m: Lcvette: morning
10:16 AM Lcvette: o/
10:16 AM Lcvette: hazzy: morning hazzy
11:08 AM roguish[m]: morning here tooooo
12:05 PM TurBoss: morning
12:28 PM hazzy-m: TurBoss: hey
01:13 PM TurBoss: hello
02:00 PM roguish[m]: hazzy: what application or program or whatever do you and JT use to do the pretty documentation pages?????
02:27 PM JT-Cave: roguish[m], which relay board do you have?
02:32 PM roguish[m]: DT-3-R6-90-4
02:32 PM roguish[m]: sorry wrong paste.
02:32 PM roguish[m]: https://www.amazon.com/gp/product/B00LW2G7V6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
02:33 PM roguish[m]: JT-Cave: what application or program or whatever do you and JT use to do the pretty documentation pages?????
02:36 PM * JamesW[m] is reading pep8
02:37 PM JamesW[m]: Argh! Its like going back to school!!
02:46 PM JamesW[m]: Is anyone using a code style checker? If so any recommendations?
03:09 PM Lcvette: hazzy: question, im trying to threadmill using linuxcnc for the first time but im getting an error message when it tries to post from fusion
03:09 PM * Lcvette sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/GcYDlZhrMiqygGFwrYneSnKY >
03:10 PM Lcvette: do you see anything that would cause the error when trying to post?
03:10 PM Lcvette: it generates the op in fusion fine, nice tool path, simulate runs great, its only when i post it complains
03:10 PM Lcvette: if i supress the thread mill op it posts through just fine
03:11 PM Lcvette: ive been trying to resolve for almost 2 hours now its kicking my ass
04:13 PM roguish[m]: woo hoo. got my $1200 from the Feds today. wife's too.
04:17 PM JT-Shop: roguish[m], thanks
04:18 PM * JT-Shop looks in his bank account to see if the slush fund money has arrived
04:44 PM hazzy-m: Whoa! I got mine weeks ago. Strange
05:03 PM JamesW[m]: tax refund? TOYS!!!
05:16 PM JamesW[m]: started thinking about an MDI queue. And have a working MDI History widget in testing and code refinement.
05:24 PM hazzy-m: JamesW: awesome! Just got home from work, getting ready to head to dev
05:28 PM JamesW[m]: I'm thinking having the history and queue widgets in a tab container makes it easy to flick between them. But that comes down to the desires of the GUI designer.
05:30 PM hazzy-m: yes, I think that makes sense
05:31 PM JamesW[m]: for example:
05:32 PM roguish[m]: hazzy: yeah, figures. aren't you in one of those red states....????? lol
05:34 PM * JamesW[m] uploaded an image: image.png (19KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ZGhZJqBaKPxsMHfzYojIyaSA >
05:34 PM * JamesW[m] uploaded an image: image.png (19KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/ywwjpMAaKZQjqBRykTnqBlaQ >
05:37 PM JamesW[m]: I think I know how I can make the queue work under the existing mechanics
05:37 PM hazzy-m: roguish: yep! I'm in one of those weird states where everyone was able to stay healthy, while also being allowed to continue to feed their families :)
05:37 PM JamesW[m]: NZ is now in lvl 2. Finally able to go the shops again
05:38 PM hazzy-m: JamesW: fantastic!!
05:38 PM JamesW[m]: Malls open
05:39 PM JamesW[m]: businesses still have to support contac tracing and we are still trying to do social distancing but things are starting to open up again
05:41 PM hazzy-m: JamesW: what is the reason for not having the queue managed by the history widget? It seems like they would end up in the history widget in the same order they are were queued...
05:41 PM JamesW[m]: because when you enter an existing command in the history is doesn't get added again
05:42 PM JamesW[m]: which means if you want to display progress of the commands that have been executed v's to be executed it would get problematic
05:43 PM hazzy-m: Ok, that makes sense
05:43 PM JamesW[m]: I'm trying to keep it clean and clear both from a code angle and from a usage angle.
05:43 PM hazzy-m: I'm more than open to changing the way history works if you think its better
05:44 PM hazzy-m: yes, I like that
05:44 PM hazzy-m: good, carry on!
05:45 PM JamesW[m]: Well for the queue I can actually use the list items as the queue and not have to matain something separate under the hood.
05:45 PM JamesW[m]: If it is combined with the history we need to have history not looking for existing instances of the command and need to maintain some flag to show what is executed and what is yet to be executed.
05:46 PM JamesW[m]: On the Queue that can be as simple as just popping them off the list so once you are done its empty
05:47 PM JamesW[m]: But heck, open to different views. I can make either pattern work and if we are ok to remove some of the "cleverness" from history I can make that work as queue as well.
05:48 PM JamesW[m]: Would probably just use a colouring style to indicate yet to be executed commands.
05:49 PM JamesW[m]: might even be possible to have a concept of a cursor which you can moved back in the history and say "start from here" and have it treat all commands at and above it as "to be run".
05:49 PM hazzy-m: That's what I was thinking could be a possibility, kinda like the sending messages in riot have a different style to indicate status
05:49 PM hazzy-m: Trying to think what would be most transparent and natural feeling for the user
05:50 PM JamesW[m]: yeah - open to advise on that front
05:51 PM JamesW[m]: ok - so I think I can do in single widget. On these assumptions/changes ....
05:51 PM JamesW[m]: 1. history widget holds exactly the history entered, no deduplication
05:51 PM JamesW[m]: 2. simple colour visual style for yet to run, running and run commands
05:52 PM JamesW[m]: 3. history order is still newest at top. so as you enter new commands they stack on the top. Meaning that when you are using it as real history you have the latest issued at the top
05:59 PM Lcvette: :o
05:59 PM Lcvette: go code go!
06:10 PM JamesW[m]: Lcvette: does what I described sound like what would work ok for a user?
06:11 PM Lcvette: JamesW: yes
06:12 PM Lcvette: i like the thing hazzy showed with the executed grayed out, the active highlights and the to be executed in plain black text
06:12 PM Lcvette: seems very intuitive and i am a big fan of intuitive
06:13 PM Lcvette: hazzy, question
06:13 PM Lcvette: my programmable coolant cannon does not seem to execute if being called by a program
06:14 PM Lcvette: works perfect if i change the tool using the on screen commands but if M6 comes from the current running program it does not execute
06:14 PM Lcvette: im stumped
06:14 PM Lcvette: /o\
06:14 PM Lcvette: ideas?
06:28 PM JamesW[m]: hazzy: For when you have a moment. Re the queue concept, here is my rough thinking. To keep things working within the existing framework you essentially have commands going on the queue (history) with an executed, executing, to execute marker. This will support styling. Now once an mdi command is in flight if you try and post another via issue_cmd you get an error as the machine is not idle. So I am thinking there is a
06:28 PM JamesW[m]: heart beat/ticker on the widget that is checking if a command is available to execute and if the interpreter is idle. If both true then issue the next command and update states in the queue. This will mean entry into the queue is via a plan QeditLine control as the widget will manage all the command issuing side of things.
06:28 PM JamesW[m]: Make sense? Any material holes in this I have missed?
06:43 PM hazzy-m: sorry, was away for a bit
06:44 PM TurBoss: Lcvette: how is the lathe?¿
06:45 PM hazzy-m: JamesW: Yes, that sounds exactly correct.
06:45 PM hazzy-m: The issue_mdi command has an ok signal that can be hooked into to tell when it's ok to issue the next command
06:46 PM Lcvette: TurBoss: getting there, close to needing the new lathe gui :o
06:46 PM TurBoss: cool
06:46 PM * Lcvette uploaded an image: tool post riser.JPEG (80KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NUHjMbAEZXCACsucrgPfUSqq >
06:46 PM * Lcvette uploaded an image: tool post riser installed.JPEG (133KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/NemqJxqzYMEFzhvpEmrKZONh >
06:47 PM Lcvette: mounting hardware will be here tomorrow
06:51 PM Lcvette: it needs the enclosure badly
06:51 PM Lcvette: makes a big mess without it
06:51 PM Lcvette: :(
07:09 PM JamesW[m]: > <@kcjengr:matrix.org> JamesW: Yes, that sounds exactly correct.
07:09 PM JamesW[m]: > The issue_mdi command has an ok signal that can be hooked into to tell when it's ok to issue the next command
07:09 PM JamesW[m]: So I can do a callback to machine_actions.issue_mdi.ok.onValueChanged(xxx) ?
07:10 PM lmclaren[m] is now known as lmclaren0978[m]
07:10 PM lmclaren0978[m] is now known as Mufdvr0978[m]
07:12 PM Mufdvr0978[m]: Hi, is there a preferred way to update a development install of pb? I can see a non development install can be updated by the installer but is this correct for a development version?
07:12 PM Lcvette: no
07:12 PM Lcvette: thats for quick installer updating only
07:12 PM Lcvette: have to do it from git
07:12 PM Lcvette: for dev
07:12 PM Mufdvr0978[m]: thanks
07:13 PM Lcvette: yup no worries
07:21 PM Mufdvr0978[m]: does this mean I am up to date?
07:21 PM * Mufdvr0978[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/elCDVFcQnBnSmHVrZWjcooJv >
07:27 PM hazzy-m: lmclaren: yes, should be good
07:27 PM hazzy-m: If your origin is kcjengr
09:26 PM Mufdvr0978[m]: thanks
11:49 PM JamesW[m]: Lcvette: what was the base machine this using? I assume you have not made the bed and everything from the ground up?
11:49 PM Lcvette: ?
11:49 PM Lcvette: oh the lathe?
11:49 PM JamesW[m]: yes
11:49 PM Lcvette: it is a 3 in 1 lathe mill drill combo
11:49 PM Lcvette: sek
11:50 PM Lcvette: https://boltontool.com/Lathes/lathe-mill-drill-combo/combo-metal-lathe-with-mill-drill
11:50 PM Lcvette: like this but was harbor freight purchase
11:50 PM Lcvette: central machinery
11:51 PM JamesW[m]: ok - cool
11:52 PM Lcvette: i am building a heavy duty drill press with the milling head
11:55 PM Lcvette: i snagged it locally pretty much new and unused, still had the cosmoline protectant all over it and was not full assembled yet
11:55 PM Lcvette: grabbed it for $900
11:55 PM Lcvette: was a sweet deal i think
11:56 PM Lcvette: came with a tool bench
11:56 PM Lcvette: which i sold because i had no need of it, sold it for $200 so have $700 in it
11:56 PM Lcvette: :D
11:56 PM Lcvette: plus the conversion parts
11:57 PM JamesW[m]: nice
11:57 PM JamesW[m]: good little deal
11:57 PM JamesW[m]: and should make a reasonable light/medium CNC lathe
11:58 PM JamesW[m]: By the time you are done with it, probably more accurate than where it started.
11:59 PM Lcvette: its a beast
11:59 PM Lcvette: it handles some pretty heafty cuts