#hazzy | Logs for 2019-01-15

Back
[00:00:19] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03master 13https://git.io/fhcSU
[00:00:21] <Not-e6c6> [02qtpyvcp] 04Pending. The Travis CI build is in progress - 13https://travis-ci.org/kcjengr/qtpyvcp/builds/479726150?utm_source=github_status&utm_medium=notification
[00:00:23] <Not-e6c6> [02qtpyvcp] 04Pending. Created - 13https://scrutinizer-ci.com/g/kcjengr/qtpyvcp/inspections/01fc759e-8df1-41f2-b443-16efad7d7c5c
[00:00:24] <Not-e6c6> [02qtpyvcp] 04Pending. Installing Code - 13https://scrutinizer-ci.com/g/kcjengr/qtpyvcp/inspections/01fc759e-8df1-41f2-b443-16efad7d7c5c
[00:00:27] <Not-e6c6> [02qtpyvcp] 04Pending. Installing Code - 13https://scrutinizer-ci.com/g/kcjengr/qtpyvcp/inspections/01fc759e-8df1-41f2-b443-16efad7d7c5c
[00:00:29] <Not-e6c6> [02qtpyvcp] 04Pending. Running - 13https://scrutinizer-ci.com/g/kcjengr/qtpyvcp/inspections/01fc759e-8df1-41f2-b443-16efad7d7c5c
[00:00:38] <hazzy-m> holy smokes
[00:00:39] <hazzy-m> LOL
[00:00:47] <hazzy-m> that is a bit much
[00:00:52] <Not-e6c6> [02qtpyvcp] 04Pending. The Travis CI build is in progress - 13https://travis-ci.org/kcjengr/qtpyvcp/builds/479726150?utm_source=github_status&utm_medium=notification
[00:01:48] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+256/-0/±0] 13https://git.io/fhcSL
[00:01:50] <Not-e6c6> [02qtpyvcp] 07traviscibot 039715c4a - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[00:03:46] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03master 13https://git.io/fhcSU
[00:05:43] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+256/-0/±0] 13https://git.io/fhcSG
[00:05:45] <Not-e6c6> [02qtpyvcp] 07traviscibot 038b05d1a - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[00:07:30] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03master 13https://git.io/fhcSU
[00:09:31] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+256/-0/±0] 13https://git.io/fhcS4
[00:09:33] <Not-e6c6> [02qtpyvcp] 07traviscibot 03c79aa43 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[05:56:00] <jthornton> morning
[06:00:56] -!- JT-qtpyvcp has quit [Quit: Leaving]
[06:18:34] -!- JT-qtpyvcp has joined #hazzy
[06:42:21] <JT-qtpyvcp> what does the trigger checkbox do in the rules editor?
[07:27:13] <JT-qtpyvcp> we are git kracken now lol
[09:11:40] <Lcvette> morning
[09:12:12] <hazzy-m> Morning
[09:14:21] <JT-qtpyvcp> I'm reworking the tutorial today to get the images all right and add a bit more content
[09:14:46] <JT-qtpyvcp> I'll push when complete so don't do any edits in there :)
[09:17:24] <hazzy-m> trigger indicates whether the rules expression should bereevaluated when the value of the channle changes
[09:18:06] <JT-qtpyvcp> I kinda thought so but wanted to verify that
[09:19:19] <hazzy-m> generaly you want to trigger, but if you use a chan whose data never changes, or one that only changes when a nother chan changes than you can save one update cycle by not triggering the expression twice
[09:19:44] <hazzy-m> excellent, thanks!
[09:20:18] <Lcvette> lcvette is looking at the git kraken
[09:20:20] <JT-qtpyvcp> that's good to know
[09:21:09] <Lcvette> hazzy should all the various screens not be contained in master?
[09:21:18] <Lcvette> to simplify things?
[09:21:54] <Lcvette> is that what we are trying to accomplish?
[09:23:00] <hazzy-m> yes, that would help, problem is there seem to be screen commits in feature branches like VKB, and I want to make sure I don't delete any of your work by accident
[09:23:48] <Lcvette> ok let me take a look
[09:24:00] <hazzy-m> thank you!
[09:28:03] <TurBoss> morning
[09:41:14] <hazzy-m> TurBoss: hey!
[09:44:33] * JT-Shop gets the fires started in the shops
[09:46:40] * hazzy-m uploaded an image: Peek 2019-01-15 09-46.gif (23KB) < https://matrix.org >
[09:46:53] <hazzy-m> added a clock :)
[09:48:29] <JT-Shop2> cool
[10:04:06] -!- Roguish has joined #hazzy
[10:42:42] <Lcvette> it appears that PB_vertical is pretty well self contained
[10:43:43] <Lcvette> if you want to merge it into master somehow and retain its unique files that should be ok
[10:43:57] <Lcvette> i think the same is ok for pb_lathe
[10:44:24] <Lcvette> so long as none of them will cross contaminate the others files
[10:44:27] <Lcvette> if that makes sense?
[10:44:53] <Lcvette> many of the folders have the same names just under a different main file
[10:45:12] <Lcvette> that is how i was instructed to split them
[10:45:51] <hazzy-m> that is what I am worried about, did you create separate folders for different layouts, or at least seperate ui files?
[10:45:58] <hazzy-m> ok, great! Then it should be ok
[10:46:12] <hazzy-m> I'll see if I can pick the commits out of VKB ..
[10:47:18] * Lcvette uploaded an image: image.png (144KB) < https://matrix.org >
[10:47:32] <JT-Shop> now it says we are going to get snow today!
[10:47:55] <Lcvette> so this is with PB_Lath checked out
[10:48:10] <hazzy-m> I think it is time for BP to leave the nest and gets it's own repo, it is pretty well self contained and it will make it much easier to work with. for example you could then run master BP with the VKB QtPyVCP branch, instead of mixing them all
[10:48:15] <Lcvette> if you notice, it has seperate folders under the examples
[10:48:34] <hazzy-m> that is perfect!
[10:48:50] <Lcvette> but the underlying folders are all named the same in each
[10:49:06] <Lcvette> meaning once you open any of them they look the same
[10:49:15] <Lcvette> there is no name differences
[10:49:47] <Lcvette> even the yml file names are all the same
[10:50:01] <Lcvette> probe_basic.yml for all 3
[10:50:01] <hazzy-m> that makes sence for now. How do you imagine a user selecting which BP layout to use? lathe could be selected automaticaly, but we could add command line option for layout
[10:50:29] <hazzy-m> and they would all install together
[10:50:47] <Lcvette> PB
[10:50:50] <hazzy-m> or you could have them separate so people install the layout they want
[10:51:12] <Lcvette> i think probably best to have them all selectable
[10:51:20] <Lcvette> ?
[10:51:23] <hazzy-m> LOL
[10:51:23] <hazzy-m> /me is not dyslexic at all :D
[10:51:37] <hazzy-m> Ok, I agree
[10:52:01] <Lcvette> currently it works because i have to specify the file path to each yml file
[10:52:10] <hazzy-m> realy the only thing that changes is the UI file
[10:52:13] <Lcvette> in the chooser
[10:52:38] <Lcvette> should i go in and save as?
[10:52:47] <Lcvette> and commit?
[10:53:03] <Lcvette> probe_basic_lathe.ui
[10:53:08] <Lcvette> ?
[10:53:27] <Lcvette> and chasnge all the other file names too?
[10:53:38] <Lcvette> i imagined that would create some broken paths
[10:53:41] <hazzy-m> that would be great, I think
[10:54:12] <hazzy-m> but they are not all on the samebranch so it might be harder than just renaming ..
[10:55:20] <Lcvette> each branch has specific graphics files
[10:55:50] <Lcvette> so that is important to make sure they remain connected properly
[10:55:58] <Lcvette> and don't get overwritten
[10:56:00] <hazzy-m> oh boy, are they in the same folder?
[10:56:03] <Lcvette> if merged
[10:57:02] <Lcvette> master has the std probe_basic graphics
[10:57:17] <Lcvette> PB_Lathe has the lathe graphics
[10:57:25] <Lcvette> PB_Vertical has the vertical graphics etc
[10:57:45] <Lcvette> when i worked on each i was always inside the correct branch
[10:58:07] <Lcvette> does that make sense
[10:59:29] <Lcvette> ok
[10:59:37] <Lcvette> so let me try and explain it more clearly
[10:59:41] <Lcvette> ready?
[10:59:52] <hazzy-m> yes, except there are some commits in VKB branch that are also for PB which are really discombobulating me LOL
[11:00:04] <hazzy-m> yes!
[11:01:23] <Lcvette> well lets start there then
[11:03:04] <Lcvette> whats giving you trouble?
[11:06:46] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03pb_lathe [+1/-0/±1] 13https://git.io/fhCwx
[11:06:48] <Not-e6c6> [02qtpyvcp] 07Lcvette 0301b859d - added flipped dimension line graphic and compiled
[11:07:22] <hazzy-m> Ok, I think I see how you have it layed out, thank you!
[11:08:12] <hazzy-m> I am going to merge both PB Lathe and PB Virtical into master, but not delete the branches. Then if you could check out master and make sure everything is OK we should be good to go
[11:08:50] <hazzy-m> if we loose anything the branches will still be there so we can revert
[11:08:52] <Lcvette> hold on a minute
[11:09:01] <Lcvette> let me take a look
[11:09:02] <hazzy-m> ok
[11:12:35] <Lcvette> looks right
[11:13:01] <hazzy-m> Ok, I'll proceed
[11:13:26] <Lcvette> so that one was all the lathe
[11:14:40] <Lcvette> if you merge pb_vertial to it, you would make sure to keep the probe_basic_lathe from that commit you just made
[11:14:44] <Lcvette> correct?
[11:15:07] <Lcvette> so everything inside that folder would remain untouched
[11:15:15] <Lcvette> ?
[11:15:35] <hazzy-m> Yes, that is what I am going to try and do
[11:15:39] <Lcvette> ok
[11:15:53] <Lcvette> then in that case we could just name it all probe_basic again
[11:15:59] <Lcvette> to make it less confusing
[11:16:01] <hazzy-m> that commit I just made was to fix a commit to VKB that should have been to PB lathe
[11:16:27] <Lcvette> oh
[11:16:36] <Lcvette> ok
[11:25:22] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03PBLathe - 13https://git.io/fhCou
[11:25:23] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 0315 commits to 03PBLathe [+164/-0/±47] 13https://git.io/fhCoz
[11:25:25] <Not-e6c6> [02qtpyvcp] 07Lcvette 03b1ab1f6 - added probe basic lathe version start
[11:25:26] <Not-e6c6> [02qtpyvcp] 07Lcvette 03d7fcb54 - added lathe tool graphic
[11:25:28] <Not-e6c6> [02qtpyvcp] 07Lcvette 03eaa4aa2 - probe basic lathe updates
[11:25:29] <Not-e6c6> [02qtpyvcp] ... and 12 more commits.
[11:25:31] <hazzy-m> Ok, I made a new branch PBLathe with only the lathe changes in it (removed the VKB stuff)
[11:25:47] <hazzy-m> can you check it out and make sure it seems OK?
[11:26:07] <hazzy-m> will do the same for PBVertical
[11:26:07] <Lcvette> sure
[11:26:18] <hazzy-m> ty
[11:29:19] <Lcvette> looks right to me
[11:32:22] <hazzy-m> fantastic!
[11:33:37] <Lcvette> if you add vertical in there now, i think all three will be updated and in one location
[11:33:53] <hazzy-m> on it!
[11:34:08] <Lcvette> werd :D
[11:34:23] <Lcvette> then your going to boot PB?
[11:37:50] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 033 commits to 03PBVirtical [+125/-0/±3] 13https://git.io/fhCKx
[11:37:52] <Not-e6c6> [02qtpyvcp] 07Lcvette 0330a6569 - Probe Basic Vertical
[11:37:53] <Not-e6c6> [02qtpyvcp] 07Lcvette 035befaff - pb vertical updates
[11:37:55] <Not-e6c6> [02qtpyvcp] 07Lcvette 03e869f0c - update
[11:37:56] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03PBVirtical - 13https://git.io/fhCou
[11:39:26] <hazzy-m> if you approve of PBVirtical I will merge both it and lathe to master
[11:39:42] <Lcvette> ok
[11:39:43] <Lcvette> checking
[11:41:27] <Lcvette> yup, looks correct!
[11:41:33] <Lcvette> whoo hoo
[11:41:45] <hazzy-m> Hurray!!!
[11:41:52] <hazzy-m> Thank you so much!
[11:43:00] <Lcvette> yup
[11:46:45] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 034 commits to 03master [+578/-0/±2] 13https://git.io/fhCiv
[11:46:47] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03ff06055 - VCP: Add Probe Basic Lathe
[11:46:48] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 0383ef30d - VCP: Add Probe Basic Vertical
[11:46:50] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03479776c - Merge branch 'PBVirtical'
[11:46:51] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03be345cc - Merge branch 'PBLathe'
[11:47:12] <hazzy-m> Ok, both lathe and virtical are in master
[11:47:19] <hazzy-m> hip hip hurray!!
[11:47:28] <Lcvette> nice!
[11:48:59] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+256/-0/±0] 13https://git.io/fhCiZ
[11:49:00] <Not-e6c6> [02qtpyvcp] 07traviscibot 0347b318c - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[11:55:36] <Lcvette> i tried to fix your name spelling
[11:55:39] <Lcvette> :(
[11:55:41] <Lcvette> i broke it
[11:57:20] <hazzy-m> Oops, what did I misspell?
[11:57:44] <Lcvette> virtical
[11:57:49] <Lcvette> vertical
[11:57:54] <Lcvette> lol
[11:58:51] <Lcvette> wont let me undo
[11:58:54] <Lcvette> :(
[11:59:04] <hazzy-m> Shoot, I checked carefully, but I guess the commit I copi6 was wrong, lol
[11:59:09] <hazzy-m> I'll try to fix
[12:09:37] <hazzy-m> I can fix it, but that is just in the merge commit, that selling error won't show up in the change log or anything important
[12:12:01] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 032 commits to 03master [+289/-0/±1] 13https://git.io/fhCXh
[12:12:03] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 035b843c0 - Merge branch 'PBVertical'
[12:12:04] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03cf54e6e - Merge branch 'PBLathe'
[12:12:11] <hazzy-m> OK, fixed
[12:12:24] <hazzy-m> I had to force push, so you will need to reset your master
[12:14:18] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+256/-0/±0] 13https://git.io/fhC1G
[12:14:19] <Not-e6c6> [02qtpyvcp] 07traviscibot 0317f4adc - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[12:14:56] <Lcvette> n54tech
[12:17:16] <hazzy-m> is that an alias for TurBoss?
[12:17:17] <hazzy-m> LOL
[12:17:27] <JT-qtpyvcp> tutorial rework half way done and lunch minute is up
[12:18:10] <hazzy-m> sorry, I made a mess of master, you will need to pull before pushing :(
[12:23:55] <JT-Shop> I always pull before pushing Jeff taught me to git pull --rebase
[12:24:37] <hazzy-m> perfect!!
[12:25:10] <JT-Shop> hmm git gui had a tool that did that will gitkraken do the same?
[12:25:20] <hazzy-m> yes
[12:25:28] <JT-Shop> ok cool
[12:25:38] * JT-Shop heads to town
[12:25:57] <hazzy-m> pull in the top, click the little arrow and click the Pull(rebase) option
[12:25:57] <Lcvette> sorry was on the line with customer and was on wrong keyboard searching
[12:25:58] <Lcvette> lol
[12:26:08] <hazzy-m> that will make it always rebase when you hit the pull arrow
[12:26:09] <Lcvette> what up lemme catch up here
[12:26:40] * Lcvette uploaded an image: image.png (216KB) < https://matrix.org >
[12:26:47] <Lcvette> thats what i am showing
[12:26:54] * hazzy-m fixed the spelling error 😇
[12:26:54] <Lcvette> what do i need to do?
[12:27:48] <hazzy-m> double click on master and reset there
[12:27:59] <hazzy-m> then push to update your remote
[12:28:51] <hazzy-m> then to keep things tidy delet BPLathe and BPVertical branches
[12:29:00] <hazzy-m> from both your local and remote
[12:29:22] * Lcvette uploaded an image: image.png (273KB) < https://matrix.org >
[12:29:35] <Lcvette> pull faST FORWArd or fordce push
[12:29:52] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 0316 commits to 03VKB [+16/-0/±30] 13https://git.io/fhCDJ
[12:29:54] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03d2a8878 - WIP on virtual keyboard
[12:29:55] <Not-e6c6> [02qtpyvcp] 07Lcvette 031bab5df - keyboard work
[12:29:57] <Not-e6c6> [02qtpyvcp] 07Lcvette 03e107886 - keyboard update graphics
[12:29:58] <Not-e6c6> [02qtpyvcp] ... and 13 more commits.
[12:30:30] <hazzy-m> force push
[12:30:52] <Lcvette> fuck
[12:30:54] <Lcvette> i pulled
[12:31:04] <hazzy-m> LOL
[12:31:22] <hazzy-m> you can reset again to kcjengr/master
[12:31:26] <hazzy-m> and then force push
[12:31:59] <Lcvette> i undo'd
[12:32:20] <Lcvette> now its a mess
[12:32:42] <hazzy-m> I can see xD
[12:33:15] <hazzy-m> reset your master to my master, and then force push should make it all right
[12:34:53] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03pb_lathe - 13https://git.io/fhCou
[12:34:54] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03pb_lathe
[12:35:01] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03PBVirtical
[12:35:02] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03PBVirtical - 13https://git.io/fhCou
[12:35:12] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03PBLathe - 13https://git.io/fhCou
[12:35:14] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03PBLathe
[12:37:16] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03dialog_launcher - 13https://git.io/fhCou
[12:37:18] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03dialog_launcher
[12:37:55] * Lcvette uploaded an image: image.png (295KB) < https://matrix.org >
[12:38:36] <hazzy-m> perfect!
[12:40:38] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 033 commits to 03master [+0/-0/±8] 13https://git.io/fhCDN
[12:40:40] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03fb894d4 - Merge remote-tracking branch 'gitlab/docstring'
[12:42:25] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03docstring - 13https://git.io/fhCou
[12:42:26] <Not-e6c6> [02qtpyvcp] 07KurtJacobson deleted branch 03docstring
[12:42:44] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03master 13https://git.io/fhCyw
[12:43:15] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+257/-0/±0] 13https://git.io/fhCyH
[12:43:16] <Not-e6c6> [02qtpyvcp] 07traviscibot 03f969bfb - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[12:44:40] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+257/-0/±0] 13https://git.io/fhCSv
[12:44:41] <Not-e6c6> [02qtpyvcp] 07traviscibot 0307f91c1 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[12:56:02] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 033 commits to 03ModuleSignals [+1/-0/±2] 13https://git.io/fhCSb
[12:56:04] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03a732000 - add signal class that can be used from modules
[12:56:05] <Not-e6c6> [02qtpyvcp] 07Kurt 03f6d7098 - WIP: module signals
[12:56:07] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03b32a0a2 - basic working channel implementation
[12:56:50] <Lcvette> ok we good?
[12:59:31] <hazzy-m> fantastic! I was starting to feel a little claustrophobic
[12:59:32] <hazzy-m> LOL
[13:00:04] <Lcvette> so what now?
[13:01:07] <hazzy-m> back to work :)
[13:01:26] <Lcvette> so are all the different ones now all merged into one?
[13:01:30] <Lcvette> master?
[13:02:31] <hazzy-m> Yes, should be all in master now
[13:02:46] <Lcvette> sweet!
[13:02:55] <Lcvette> if i work on them
[13:02:59] <Lcvette> where do i do it?
[13:03:05] <Lcvette> in master?
[13:03:14] <Lcvette> or in those little branches
[13:03:18] <hazzy-m> yea, that is good for now
[13:03:33] <hazzy-m> delete those little branches, both from your local and remote=
[13:03:34] <Lcvette> and you are going to boot PB?
[13:04:06] <hazzy-m> yes, we should start working on booting it
[13:04:16] <Lcvette> even though it isn't finished?
[13:04:47] <hazzy-m> do you want to host it on your account, or do you mind if I do?
[13:05:00] <hazzy-m> yes, it should make it much easier to work on
[13:05:12] <Lcvette> you host it
[13:05:21] <Lcvette> i don't know how to do anything on it
[13:05:27] <Lcvette> better you maintain it i think
[13:05:33] <hazzy-m> haha, ok!
[13:05:43] <Lcvette> don't you?
[13:06:20] <hazzy-m> yes, just didn't want to take it if you wanted to have it under your account
[13:07:55] <hazzy-m> there are a few things we will have to work out, for example, is are the ATC widgets part of PB, or do they belong in the main QtPyVCP repo ..
[13:07:55] <Lcvette> i would break it
[13:09:17] <hazzy-m> My feeling is they are pretty PB specific, since they include all the PB images and styling
[13:09:56] <Lcvette> hazzy, i don't care
[13:10:01] <hazzy-m> booting PB is not height priority, so we can sleep on it
[13:11:13] <Lcvette> but i have one stipulation, it is not to be used elsewhere until PB is 100% completed and up and running
[13:11:41] <Lcvette> after that i don't care who uses it but PB has priority
[13:12:20] <hazzy-m> Yes, I completely agree with that, we are focusing on getting PB out
[13:13:04] <Lcvette> that goes for all the graphics i made
[13:13:20] <Lcvette> use them if you want but only after PB
[13:13:23] <Lcvette> :D
[13:13:28] <Lcvette> it must be the first
[13:13:32] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 036 commits to 03Lathe_Touch_off [+0/-0/±34] 13https://git.io/fhCHc
[13:13:34] <Not-e6c6> [02qtpyvcp] 07TurBoss 030216162 - add signals to qml
[13:13:35] <Not-e6c6> [02qtpyvcp] 07TurBoss 03f316e5a - Merge remote-tracking branch 'kcjeng/Lathe_Touch_off' into Lathe_Touch_off
[13:13:37] <Not-e6c6> [02qtpyvcp] 07TurBoss 03a3b5cd2 - select tool by external signal
[13:13:38] <Not-e6c6> [02qtpyvcp] ... and 3 more commits.
[13:13:49] <Lcvette> ok i need to get some orders out here
[13:13:54] <Lcvette> will be back on latyer this evening
[13:14:16] <hazzy-m> sounds good
[13:14:23] <hazzy-m> cu
[13:19:45] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 035 commits to 03NewATC [+36/-0/±7] 13https://git.io/fhCHS
[13:19:46] <Not-e6c6> [02qtpyvcp] 07TurBoss 031a74ee9 - Get DynATC from old branch
[13:19:48] <Not-e6c6> [02qtpyvcp] 07TurBoss 03beeea21 - doesn't crash on designer
[13:19:49] <Not-e6c6> [02qtpyvcp] 07TurBoss 038451c1e - embed DynACT on PB
[13:19:51] <Not-e6c6> [02qtpyvcp] ... and 2 more commits.
[14:42:37] * JT-qtpyvcp takes 5 while the pipe cools oof
[14:42:41] <JT-qtpyvcp> off even
[15:01:26] <TurBoss> hello
[15:01:33] <TurBoss> any memorable event?
[15:01:36] <TurBoss> backlog is long
[15:19:28] <JT-qtpyvcp> yippie done with the make over on the tutorial, I'll probably think of a few more things to add by the morning so I'll pull/push then
[15:20:18] * JT-qtpyvcp goes back to work
[15:28:32] <hazzy-m> hurray!
[15:30:10] <JT-Shop2> it looks much better this time around
[15:30:37] <JT-Shop2> I think anyone can make a functional VCP in less than 20 minutes now
[15:39:28] -!- kreng has joined #hazzy
[15:44:02] -!- kreng has quit [Client Quit]
[16:17:31] -!- mode/#hazzy [+o hazzy-m] by ChanServ
[16:19:04] <hazzy-m> JT-Shop2: that is awesome!
[16:20:12] <TurBoss> great!!
[16:26:52] <TurBoss> hazzy: did you somethign with th ATC thing?
[16:27:37] <hazzy-m> no, just rebased it on master
[16:27:40] <hazzy-m> it was a little old
[16:27:51] <TurBoss> ok
[16:28:06] <TurBoss> any news on the PR needed to make it work?
[16:28:20] <hazzy-m> not that I have seen :(
[16:28:28] <TurBoss> :(
[16:28:39] <TurBoss> do you remember wich is?
[16:31:48] <hazzy-m> https://github.com
[17:06:15] <JT-qtpyvcp> do you have a ngcgui like tool?
[17:07:39] <JT-qtpyvcp> shouldn't the MDIEntry be disabled until power is on and if no force homing is off homed
[17:08:10] <hazzy-m> to an extent, the SubCall button will fill in NGCGUI format subroutine arguments from widgets that have matching names in the active window
[17:09:11] <hazzy-m> so that is like NGCGUI, but it does not creat the input boxes the NGCGUI does, at least not yet
[17:09:35] <hazzy-m> Yes, MDI should certainly be disabled untill homed, and when the machine is not idle
[17:09:54] <hazzy-m> I'll get on it
[17:10:19] <JT-qtpyvcp> ok I was just wondering about that...
[17:11:45] <hazzy-m> thank you for mentioning those things, I'm so focused on dev that I don't get to play with the widgets much to notice that stuff
[17:19:27] <JT-qtpyvcp> that's my job lol
[17:20:15] <JT-qtpyvcp> how do you clear the backplot?
[17:20:38] <hazzy-m> hehe, double right click
[17:20:52] <hazzy-m> need to make that a little more intuitive
[17:20:54] <JT-qtpyvcp> how do you do that with a touch screen?
[17:21:09] <hazzy-m> use your right hand
[17:21:11] <hazzy-m> LOL
[17:21:18] <hazzy-m> guess you can't ...
[17:21:32] <hazzy-m> the back plot needs serious work
[17:21:41] <JT-qtpyvcp> I tried that and it said operation invalid lol
[17:22:04] <JT-qtpyvcp> did you make the backplot?
[17:22:33] <hazzy-m> no, I stole it from QtPyVCP, it's one of the only things I have not redone
[17:22:40] <hazzy-m> QtVCP*
[17:23:15] <JT-qtpyvcp> where is it?
[17:23:27] <JT-qtpyvcp> nm
[17:32:52] <JT-qtpyvcp> what would be the modern way to have a backplot?
[17:35:14] <hazzy-m> TurBoss worked on a VTE version, but I think that the current OpenGL approach is fine, but it needs to be updated
[17:35:52] <hazzy-m> It was written before hardware OpenGL support was common, so it uses a very old GL compatability layer that is not full featured
[17:35:53] <JT-qtpyvcp> ok, just wondering
[17:37:55] <TurBoss> yo
[17:39:43] <TurBoss> new VTK would rise
[17:39:46] <TurBoss> lol
[17:44:51] <JT-qtpyvcp> machine_actions.py line 644 should be CMD.unhome(jnum)
[17:46:00] <hazzy-m> instead of pass?
[17:46:10] <hazzy-m> not sure why I never finished those
[17:46:26] <JT-qtpyvcp> well pass needs fixing as well
[17:47:33] <hazzy-m> my line numbers don't line up with yours I think
[17:47:42] <hazzy-m> I merged docstrings ..
[17:47:50] <hazzy-m> must be why
[17:48:04] <JT-qtpyvcp> ah ok in def _unhome_joint
[17:48:53] <hazzy-m> oh, yes, good catch!
[17:54:56] <JT-qtpyvcp> yea I was trying to figure out how to unhome an axis
[17:56:53] <JT-qtpyvcp> hmm I need to make a jog speed slider I think
[17:57:29] <hazzy-m> there is an action fro one, but it is not ideal
[17:57:43] <hazzy-m> i've been working on it
[17:59:04] <hazzy-m> I am completely reworking the DataChannels, which will make that sort of think much easier
[17:59:23] <JT-qtpyvcp> nice
[17:59:57] <JT-qtpyvcp> it's like anything you do it once then see a better way so you do it again
[18:00:25] <hazzy-m> exactly!
[18:00:31] <hazzy-m> it will be much more pythonic
[18:01:49] <hazzy-m> instead of status:task_state?text it will be str(status.task_state)
[18:02:19] <hazzy-m> tooltable:current_tool?diameter will be tooltable:current_tool['diameter']
[18:02:34] <JT-qtpyvcp> much nicer
[18:02:51] <hazzy-m> yea, should be much more intuitive
[18:03:36] <JT-qtpyvcp> I see a lot of docstrings I need to add lol
[18:03:46] <hazzy-m> also will support doc strings and chan name auto completion in the rules editor
[18:04:08] <JT-qtpyvcp> ohh that is nice
[18:10:59] <TurBoss> JT-qtpyvcp: where is your fork of qtpyvcp hosted github gitlab?
[18:11:32] <JT-qtpyvcp> I didn't fork it
[18:11:41] <JT-qtpyvcp> I use github
[18:11:51] <hazzy-m> he pushed directly
[18:11:55] <TurBoss> fork and make pullreques
[18:11:55] <TurBoss> t
[18:12:00] <TurBoss> of merges
[18:12:02] <TurBoss> :D
[18:12:02] <hazzy-m> I think we should all switch to github ..
[18:12:11] <TurBoss> ya
[18:12:43] * hazzy-m is bad at making feature branches
[18:12:45] <hazzy-m> lol
[18:12:57] <TurBoss> why?
[18:13:04] <TurBoss> isn't much hard?
[18:13:06] <hazzy-m> lazy :D
[18:13:10] <TurBoss> ah
[18:13:29] <hazzy-m> I realy need get better at doing it, I always forget
[18:24:19] -!- Roguish__desk has quit [Read error: Connection reset by peer]
[18:24:42] -!- Roguish__desk has joined #hazzy
[18:25:06] -!- Roguish_ has joined #hazzy
[18:25:16] -!- Roguish has quit [Ping timeout: 264 seconds]
[18:25:17] Roguish_ is now known as Roguish
[18:51:43] <JT-qtpyvcp> so while the emc docs are building I have a jog speed slider working any hints on how to display the percentage?
[18:53:24] <hazzy-m> you can't at the moment, but hang tight, it is in the works
[18:53:46] <JT-qtpyvcp> ok
[18:54:02] <hazzy-m> the jog speed slider it what made me rewrite the data channels
[18:54:02] <hazzy-m> :D
[18:54:21] <JT-qtpyvcp> what about feed override and rapid override?
[18:56:30] <hazzy-m> those work
[18:56:41] <hazzy-m> status:rapidrate
[18:56:56] <JT-qtpyvcp> ok cool
[19:11:35] <JT-qtpyvcp> hmm the first saved entry in the mdi entry does not run
[19:22:30] <JT-qtpyvcp> odd that the feed rate slider is at 1/2 and shows 100% and goes to 200% even though the slider max is 100
[19:24:07] <JT-qtpyvcp> rapid seems to be capped at 100% which may not be bad but feed override should be able to set the slider max to say 120
[19:28:13] <jthornton> time to retire to the upstairs
[19:55:37] <Lcvette> jthornton: on pb?
[19:55:45] <Lcvette> lol
[19:58:52] <Lcvette> just another unfinished quirk in PB
[19:58:52] <hazzy-m> jthornton slider Max and min values are set in the ini
[19:58:53] <Lcvette> :(
[19:59:12] <hazzy-m> It should be working right
[19:59:33] <hazzy-m> One of the few things I think is not broken 😂
[19:59:33] <Lcvette> what about the jog rate?
[19:59:46] <hazzy-m> Working on it
[19:59:49] <Lcvette> is that wehat he meant?
[20:00:32] <hazzy-m> Think he meant the feed override
[20:00:37] <Lcvette> 3027n kisa sdportasge wheels
[20:32:41] -!- Roguish has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
[22:34:15] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03DataChannel - 13https://git.io/fhCou
[22:34:16] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 033 commits to 03DataChannel [+0/-0/±3] 13https://git.io/fhWEc
[22:34:18] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 036c32cad - BUG: fix unhome action in machine_actions
[22:34:19] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 036e10537 - log plugin Initialization and termination
[22:34:21] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 034dc75b3 - terminate plugins in reverse order that they were initialized
[22:34:53] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 033 commits to 03master [+0/-0/±3] 13https://git.io/fhWE8
[22:35:30] <Not-e6c6> [02qtpyvcp] 07KurtJacobson created branch 03master 13https://git.io/fhWE4
[22:37:20] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+257/-0/±0] 13https://git.io/fhWER
[22:37:22] <Not-e6c6> [02qtpyvcp] 07traviscibot 03f442a26 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
[23:49:23] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fhWz2
[23:49:25] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 03fa3ab02 - BUG: fix regression that prevents error dialog from showing
[23:51:04] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+257/-0/±0] 13https://git.io/fhWzV
[23:51:05] <Not-e6c6> [02qtpyvcp] 07traviscibot 03ec9a631 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages