#hazzy | Logs for 2019-03-23

Back
[01:28:03] * hazzy-m has been playing with Mill Touch
[01:28:21] <hazzy-m> the MDI and help popup is awesome!
[01:28:50] <Lcvette> \o/
[01:29:06] <Lcvette> Hurray!
[01:29:13] <Lcvette> Yeah it's pretty cool
[01:34:05] <hazzy-m> https://youtu.be
[01:34:21] <hazzy-m> So cool I had to make a vid lol
[01:34:32] <Lcvette> Nice!
[04:25:30] <Not-e6c6> [02qtpyvcp] 07TurBoss pushed 031 commit to 03ATC [+0/-0/±1] 13https://git.io/fjJ8a
[04:25:31] <Not-e6c6> [02qtpyvcp] 07TurBoss 03b5610ab - fix carousel when changing tabs
[06:06:16] <JT[m]1> morning
[06:10:21] <jthornton> https://youtu.be
[07:05:01] <biqut2> just watched your video, really like the context sensitive gcode information
[07:05:51] <JT[m]1> thanks
[07:07:57] <JT[m]1> hopefully I can finish that this morning
[07:10:43] <biqut2> I'm a machinist by trade and run several different machines daily with different controls, part of my job is training other operators and I'm very much interested in designing a very user friendly control without sacrificing any functionality. I actually saw your GUI on the linuxcnc forum and that what lead me here to take qtpyvcp for a spin.
[07:14:49] <biqut2> I spend a lot of time programming macros for various repetitive operations and would like to do something like your MDI screen to interface with different macros, NGCGUI is nice but just not quite there as far a versatility and user friendliness, Something like a cross between fanucs manual guide i and milltronics conversational.
[07:25:26] <JT[m]1> I agree with you about ngcgui, I use it but it's limiting. I'm not familar with either fanuc or milltronics, I'm a machine designer but I do have a machine shop but have never worked in one
[07:44:09] <biqut2> What type of machines do you design?
[07:55:51] <silopolis[m]> Hello
[07:58:29] <silopolis[m]> @jt-m:matrix.org: excellent video 👍
[07:59:43] <JT[m]1> assembly machines and process machines like inline cleaners and packers for bulk products like nails
[08:00:07] <JT[m]1> silopolis: hazzy did the video 😁
[08:00:28] <silopolis[m]> @biqut2
[08:01:11] <silopolis[m]> @hazzy:matrix.org: sorry 🙂
[08:02:33] <silopolis[m]> @biqut2: that'd surely be great, some kind of extended conversational UI?
[08:02:40] <biqut2> Ah okay, those machines are very interesting as well. I'm always trying to optimize to nth degree and that what those machines are all about.
[08:03:33] <biqut2> @silopolis[m], yes a conversational UI with more power and flexibility
[08:06:07] <biqut2> for example we use macros and system parameters to automate 99% of the jobs we run on a daily basis, my operator would only need to input the location and dimensions of a feature like a bore, boss, pocket, drilled/tapped hole and the machine does all the necessary calculations when they press the big green button.
[08:09:45] <silopolis[m]> 👍👍
[08:10:18] <biqut2> the milltronics controls have a very user friendly conversational interface, no doubt since Hurco now owns them, the new 9000 control has a lot of nice feature including tri-cordial tool paths on the control but its still very limiting, mainly on entry/exit strategies, contrast that to the fanucs, not every machine has manual guide i, also I have to give my operators a key to show which parameters correlate to the desired input. There is an addon
[08:10:18] <biqut2> from fanuc that allows the creation of a gui parameter interface but again its not on every machine as it costs extra $$
[08:12:49] <silopolis[m]> Have a friend who just brought a superb router but with an old NC. Talking with him yesterday, thought QtPyVCP would be a great framework to develop this kind of features for woodworkers like a box maker, cabinet, drawer...
[08:15:39] <biqut2> certainly, I have macros written for a router that I own, basically I design my parts parametrically and then alter a few key variable such as length, width, depth and have the macro generate the actual code so that if i need to make different size items suck as drawers, shelves, boxes, etc the work is already done and i can have the machine running in seconds.
[08:30:19] <silopolis[m]> Exactly!
[08:44:38] <JT[m]1> finally got that damn setup.py and manifest.in sorted out lol
[09:41:19] <Lcvette> morning
[09:43:58] <Lcvette> turboss \o/ Hurray!! 😃 Disco Disco!!
[09:44:07] <Lcvette> you fixed the atc issue!
[09:44:14] <Lcvette> whoo hoo!!!
[09:46:39] <Lcvette> JT: whats that?
[10:04:02] <JT[m]1> Lcvette: better watch out your next LOL
[10:04:18] <Lcvette> whats that?
[10:04:19] * JT[m]1 got mill_touch to install correctly
[10:04:23] <Lcvette> im working on mill touch
[10:04:25] <Lcvette> :O
[10:04:43] <Lcvette> im fixing things
[10:05:54] <JT[m]1> on your branch or master?
[10:06:10] <Lcvette> my branch
[10:07:22] <JT[m]1> I've been trying to finish up the help text for the smart mdi tab
[10:07:35] <Lcvette> nice!
[10:07:49] <JT[m]1> it's working out better than I thought
[10:08:02] <JT[m]1> and I have some more ideas for it
[10:08:23] <JT[m]1> hazzy: any thoughts on sending hal commands?
[10:08:27] <Lcvette> talk to me goose
[10:15:38] <hazzy-m> morning!
[10:15:50] <hazzy-m> Yes, getting reading to work on HAL now
[10:21:15] <JT[m]1> morning
[10:21:29] <JT[m]1> cool, can't wait to see that
[10:21:43] <JT[m]1> I liked your video 😁
[10:22:04] <Lcvette> sweet, will that do the probe?
[10:22:21] <JT[m]1> hazzy: I sorted out all my problems with mill_touch installed with pip and the uninstall issue
[10:37:25] <hazzy-m> Excellent!
[10:38:00] * hazzy-m has to do some laundry real quick lol
[10:44:09] <Lcvette> JT, what am i next?
[10:45:37] <roguish[m]> JT: really like and appreciate this: https://jethornton.github.io
[10:45:59] <roguish[m]> hazzy: take note......
[10:46:13] <hazzy-m> Lcvette I think he means with ProbeBasic 👹
[10:46:46] <Lcvette> o/
[10:46:56] <hazzy-m> roguish I did last night!
[10:47:00] <Lcvette> you mean fix?
[10:47:02] <hazzy-m> o/
[10:47:06] <Lcvette> :D
[11:10:55] <JT[m]1> Yep your next Lcvette
[11:12:18] * JT[m]1 is shopping
[11:13:09] <Lcvette> :D
[11:38:27] <Lcvette> hazzy, im looking through JT's dark.qss and there are alot of different commands in here
[11:38:43] <Lcvette> for example instead of px its ex
[11:38:45] <Lcvette> ?
[11:41:57] <hazzy-m> those are standard HTML/CSS commands
[11:42:28] <Lcvette> so can they be mixed
[11:42:32] <Lcvette> or no?
[11:42:34] <hazzy-m> px is the height of the font in pixles, ex is the x-height of the font in pixles, both ot which are absolute values
[11:42:59] <Lcvette> x-height?
[11:43:06] <Lcvette> only in the x axis?
[11:43:07] <hazzy-m> em is the fraction size of the font relative to the base font size (I think )
[11:43:18] <hazzy-m> LOL
[11:43:18] <hazzy-m> sek
[11:43:39] <Lcvette> so in this case its used for borders too
[11:43:45] * hazzy-m things Lcvette didn't take calligraphy
[11:43:50] <Lcvette> so em is fractional pixels
[11:43:54] <hazzy-m> hmmm'
[11:44:23] * hazzy-m uploaded an image: image.png (86KB) < https://matrix.org >
[11:44:25] * Lcvette sent a long message: < https://matrix.org >
[11:45:08] <hazzy-m> interesting, Iv'e never used ex for things other than font size, not sure how that works exactly
[11:45:31] <Lcvette> was new to me too
[11:45:43] <Lcvette> not even sure how JT made this QSS
[11:45:47] <Lcvette> it huge
[11:45:50] <Lcvette> lol
[11:46:24] <Lcvette> 1615 lines long
[11:46:43] <Lcvette> :O
[11:48:11] <hazzy-m> shhh, don't tell, but he stole it
[11:48:52] <Lcvette> ?
[11:55:32] <JT-Shop> lol
[12:02:36] <JT[m]1> I'll slowly remove the ex for borders as I assimilate it into the collective
[12:04:48] <Lcvette> right now its very difficult to manipulate
[12:05:22] <Lcvette> im not even sure where to make changes to things
[12:05:32] <Lcvette> style sheet doesn't seem to work
[12:06:19] <Lcvette> so im sure its being over ridden in a qss somewhere but thats a websters dictionary thick file of none descript items
[12:06:39] <JT[m]1> just start a new qss
[12:07:07] <JT[m]1> did you notice some of the base widgets style starts with a .
[12:07:24] <JT[m]1> like .SomeBaseWidget
[12:07:49] <Lcvette> no
[12:08:06] <Lcvette> where are you referring?
[12:08:40] <JT[m]1> that means to use the style for only that widget and not for any subclassed widget of that widget
[12:09:33] <JT[m]1> look in dark1.qss line 666
[12:10:55] <JT[m]1> dark1.qss is a better place to start it only has 276 lines including the qtpyvcp specific ones
[12:11:06] <Lcvette> my dark1.qss only goes to 263
[12:11:37] <JT[m]1> I've been working on it :)
[12:13:38] <Lcvette> i amnot seeing anything like that in the qss im working in
[12:13:54] <JT[m]1> which one are you working in?
[12:14:32] <Lcvette> dark.qss
[12:14:39] <Lcvette> the only big one
[12:14:56] <Lcvette> thats the only one with more than 263 lines
[12:15:10] <Lcvette> its in the ui file
[12:15:52] <JT[m]1> well hell I forgot to delete them...
[12:16:03] <Not-e6c6> [02qtpyvcp] 07KurtJacobson pushed 0321 commits to 03Settings [+17/-3/±46] 13https://git.io/fjJzy
[12:16:04] <Lcvette> delete it?
[12:16:05] <Not-e6c6> [02qtpyvcp] 07KurtJacobson 038cac425 - WIP object settings
[12:16:14] <Lcvette> dark.qss and light.qss
[12:16:21] <Lcvette> in the ui file?
[12:16:43] <JT[m]1> yea the qss files are in mill_touch/configs/mill_touch_sim/themes
[12:17:07] <JT[m]1> no wonder we are confused...
[12:17:19] <Lcvette> how about style.qss?
[12:17:37] -!- travis-ci has joined #hazzy
[12:17:38] <travis-ci> kcjengr/qtpyvcp#843 (Settings - 8cac425 : Kurt Jacobson): The build was broken.
[12:17:39] <travis-ci> Diff view : https://github.com
[12:17:39] <travis-ci> Build details : https://travis-ci.org
[12:17:39] -!- travis-ci has parted #hazzy
[12:17:46] <JT[m]1> I don't use that one either
[12:18:24] * JT[m]1 sent a long message: < https://matrix.org >
[12:18:38] <JT[m]1> wonder why that came out bold...
[12:19:37] <JT[m]1> except that is wrong for a git pull now :(
[12:19:45] * Lcvette sent a long message: < https://matrix.org >
[12:20:00] <Lcvette> thats whats in my ini
[12:20:18] <JT[m]1> that is correct as well
[12:20:36] <Lcvette> k
[12:20:57] <JT[m]1> #STYLESHEET = ../../../mill_touch/themes/dark1.qss
[12:21:19] <JT[m]1> this just says back up 3 directories then drill down to dark1.qss
[12:21:57] <Lcvette> so i should change it?
[12:25:28] <JT[m]1> if your going to add another stylesheet to mill_touch and want to see that when you run the sim then yes you want to point to that stylesheet and not the one in linuxcnc/configs/mill_basic
[12:25:56] <Lcvette> k
[12:26:24] <JT[m]1> just copy dark1 or dark2 and name it dark3 then in the ini point to it
[12:27:09] <JT[m]1> hmm I think I can leave the mill_touch/themes and copy from there to the config during the install so that would be a cleaner way
[12:27:30] <hazzy-m> wonder if we should add a --style option to the aplication, and add a styles section the YAML file were you can specify a style name and a .qss file, then you would not have to specify the whole path in the INI
[12:28:09] <JT[m]1> where would the styles be?
[12:28:35] <JT[m]1> how would that work for an installed gui like mill_touch?
[12:28:41] <hazzy-m> they could then be installed in the .local dir woth the rest of the VCP
[12:28:52] <roguish[m]> hey, about file organization. where should a user's custom .ui file live? in the config directory? or where?
[12:28:59] <JT[m]1> that would work in the lib directory?
[12:29:27] <roguish[m]> JT, maybe you have an idea 'cause of your recent file loss...
[12:29:28] <hazzy-m> roguish: if it is machine specific it shold go in the config dir
[12:29:49] <hazzy-m> JT: yes
[12:30:01] <roguish[m]> should that include any specific support file? like the .yml?
[12:30:44] <hazzy-m> yes, then you will add a machine specific .yml file to your config folder and specify it in the INI
[12:31:05] <hazzy-m> that yml file is where you will tell QtPyVCP to load your extra UI file
[12:31:17] <roguish[m]> ya may want to outline this in your install instructions.
[12:31:47] <hazzy-m> yes, the yml config is not well documented at all
[12:32:51] <JT[m]1> dang I've been chasing my tail for a while looking for a link error in the emc docs and finally found it...
[12:33:11] <hazzy-m> hurray!
[12:34:32] <JT[m]1> I forgot about the hand written gcode.html file... and when I changed a link that one failed to pass the linkchecker
[12:35:24] <JT[m]1> I would need an example of what roguish is talking about 🙂
[12:35:52] <hazzy-m> yes, I will make an example
[12:36:09] <roguish[m]> just some words or directory structure diagram as to where files should reside.
[12:37:33] <hazzy-m> roguish: there is a little info here: https://qtpyvcp.kcjengr.com
[12:39:17] -!- biqut2 has quit [Remote host closed the connection]
[12:39:53] <roguish[m]> thanks.
[12:41:29] <roguish[m]> ok, so i am going to run bp2_touch (my form of JT's mill_touch) with a DRO ui in a separate window. I can specify the dro ui in the .yml file. what name should the .yml file have and how is it specified in the .ini?
[12:41:57] <roguish[m]> should the .yml have the same name as the primary ui?
[12:42:49] <hazzy-m> you can name the yml file whatever you like, `custom_config.yml` would be a decent name
[12:42:54] <hazzy-m> yes, that is fine too
[12:43:03] <hazzy-m> actualy probably better
[12:43:47] <hazzy-m> then in the [DISPLAY] section of the INI add `CONFIG_FILE = custom_config.yml`
[12:43:53] <hazzy-m> or whatever you called it
[12:46:30] <roguish[m]> GOT IT.
[12:48:05] * roguish[m] uploaded an image: image.png (327KB) < https://matrix.org >
[12:48:30] <hazzy-m> Nice!
[12:49:03] <roguish[m]> I realize that all this file naming and location stuff is pretty arbitrary, but good examples are worth hours of effort and frustration.....
[12:49:15] <Lcvette> JT: where are the buttons styled? because when i make changes to the QPushButton section in the qss it doesn't take effect
[12:50:23] <roguish[m]> JT: hazzy thanks.
[12:51:09] <hazzy-m> np, you had it done before I could finish typing instructions lol
[13:00:57] <JT-Shop2> Lcvette: be down in the beer cave in a bit
[13:01:14] <Lcvette> k
[13:08:57] <JT[m]1> which button, which stylesheet
[13:09:16] <JT[m]1> roguish: nice!
[13:10:33] * Lcvette uploaded an image: Screenshot_2019-03-23_13-10-18.png (57KB) < https://matrix.org >
[13:10:57] <Lcvette> i would like to add some background color to the buttons but nothing seems to work
[13:11:45] <JT[m]1> which button? you have qpushbuttons, actionbuttons and mdi buttons on the bottom row
[13:12:04] <JT[m]1> this is a good reference https://doc.qt.io
[13:12:06] <Lcvette> all the black background buttons
[13:12:23] <JT[m]1> which qss file?
[13:12:38] <Lcvette> im in a saved file lcvette.qss
[13:12:50] <Lcvette> this is a copy of dark1
[13:12:59] <JT[m]1> ok
[13:14:04] -!- biqut2 has joined #hazzy
[13:14:22] <JT[m]1> QPushButton{... will do any push button that is not overriden by a more finite selector
[13:14:54] <Lcvette> if that were the case, there would be a background
[13:15:04] <JT[m]1> ActionButton{... overrides the QPushButton{
[13:15:18] <roguish[m]> where / how is the 'dark' theme come from?
[13:15:44] <Lcvette> the ini setting
[13:15:45] <JT[m]1> because it's a more finite selector
[13:15:47] <JT[m]1> roguish: don't ask lol
[13:15:53] <roguish[m]> I see a theme can be spec'd in the .ini file, but where does it come from? is it inherent in the OS?
[13:15:58] <JT[m]1> oh how does one use it
[13:16:07] <JT[m]1> no
[13:16:08] <Lcvette> comes from a .qss file
[13:16:26] <roguish[m]> can you share the .qss file?
[13:16:31] <Lcvette> you have it
[13:16:42] * JT[m]1 sent a long message: < https://matrix.org >
[13:16:44] <Lcvette> its in m,ill_touch/themes
[13:17:00] <JT[m]1> roguish: if you pulled this morning you have it
[13:17:25] <JT[m]1> Lcvette: see the above it overrides anything you do in qpushbutton
[13:17:48] <Lcvette> to change between them just change the file name in the ini to a different .qss file in the themes folder
[13:18:03] <JT[m]1> if you comment out background-color and no other selector is in effect then the qpushbutton will apply
[13:18:17] <Lcvette> i changed that background color and it had zero effect
[13:19:03] <Lcvette> I think you may want to consider a different method
[13:19:24] <Lcvette> maybe have ALL buttons have a standard format and then use custome formatting for specific button groupings
[13:20:07] <JT[m]1> that's what I'm working toward and anything below /* End of QtPyVcP specific styles */ will be deleted in the end
[13:20:10] <Lcvette> that way you can make global changes to all buttons while excluding the customized buttons such as estop and power etc
[13:22:15] * Lcvette sent a long message: < https://matrix.org >
[13:22:51] <Lcvette> thats from probe basics qss
[13:22:55] <Lcvette> as an example
[13:23:36] <JT[m]1> Lcvette: it would be much easier to just start from scratch and add one item at a time to your new qss and just refer to the other ones for syntax
[13:23:56] <Lcvette> ok
[13:24:56] <JT[m]1> actually that is all they are there for are syntax and ideas etc. eventually all the ones I found will be deleted
[13:25:24] <JT[m]1> but for now we have something sorta reasonable to use
[13:25:29] <roguish[m]> Lcvette: could you show exactly the line that calls the 'dark.qss' in your .ini file, please.
[13:25:52] <JT[m]1> roguish: did you pull this morning?
[13:25:59] <roguish[m]> yes.
[13:26:01] * Lcvette sent a long message: < https://matrix.org >
[13:26:05] <Lcvette> bottom line
[13:26:11] <JT[m]1> you don't have dark.qss anymore then
[13:26:26] <Lcvette> mine shows lcbvette.qss because im on a customized file
[13:26:41] <JT[m]1> roguish: did you do a git checkout?
[13:26:45] <Lcvette> but you should select dark1.qss, dark2.qss, dark3.qss
[13:27:06] <roguish[m]> JT: did a git pull
[13:28:07] <JT[m]1> look in mill_touch/configs/mill_touch_sim/themes and copy one to your lcnc config directory
[13:28:31] <roguish[m]> i copied the dark.qss to my config directory and called the file explicitly with the full path/file name. and no worky.
[13:28:41] <JT[m]1> then just say STYLESHEET = dark1.qss in the display section
[13:29:00] <JT[m]1> roguish: don't use that one
[13:29:47] <roguish[m]> only have dark, and light
[13:30:18] <JT[m]1> look in mill_touch/configs/mill_touch_sim/themes and copy one to your lcnc config directory
[13:32:56] * roguish[m] uploaded an image: image.png (97KB) < https://matrix.org >
[13:34:06] <JT[m]1> dang that is hard for old guys to read but yea looks like you have an error
[13:36:59] <roguish[m]> i'll beat it to death, but it's still not working. have put in the file path explicitly, and still no success.
[13:37:10] <JT[m]1> did you find the qss files like 5 of them?
[13:37:31] <roguish[m]> yes. copied them to my config directory.
[13:37:46] <Lcvette> no need to copy to config directory
[13:38:05] * roguish[m] uploaded an image: image.png (50KB) < https://matrix.org >
[13:38:05] <Lcvette> just set path to the mill_touch/themes directory
[13:38:55] <JT[m]1> if it's in the config directory then STYLESHEET = dark1.qss is all you need
[13:39:39] <JT[m]1> Lcvette: that directory is gone...
[13:39:47] <roguish[m]> same error.
[13:40:36] <roguish[m]> and if i comment out the STYLESHEET line, it all works fine.
[13:41:52] <JT[m]1> STYLESHEET = ../../../mill_touch/configs/mill_touch_sim/themes/dark4.qss
[13:42:08] <JT[m]1> that's what I'm using at the moment
[13:42:22] <JT[m]1> if the path is correct then it should just work
[13:43:10] <JT[m]1> if dark1.qss is in ~linuxcnc/configs/bp2_mill all you need is STYLESHEET = dark1.qss
[13:44:15] <roguish[m]> it does not work. either way. any way.
[13:45:11] <roguish[m]> oh well. i'll figure it out later. thanks. gotta do a bit of wiring on the mill, and move the touch screen out to the mill also.
[13:45:34] <JT[m]1> comment out config_file and see if that is doing something to it
[13:47:10] <roguish[m]> good guess, but no luck.
[13:47:15] * JT[m]1 uploaded an image: Screenshot at 2019-03-23 12-46-42.png (45KB) < https://matrix.org >
[13:47:24] * JT[m]1 sent a long message: < https://matrix.org >
[13:47:46] <JT[m]1> Lcvette: that is the entire qss file...
[13:47:47] <roguish[m]> i kinda like Lcvette's ....
[13:48:17] <JT[m]1> on those others they had border style for example all over the place lol
[13:48:28] <Lcvette> nice!
[13:48:33] <JT[m]1> roguish: I only set the style for the buttons and nothing else
[13:48:58] <Lcvette> i am robbing probe basics and modifying
[13:48:59] <JT[m]1> so for disabled state only set what you want to change
[13:49:25] <Lcvette> and will nuke all unecessary crap
[13:49:39] <JT[m]1> we all going to be style monkeys in a while
[13:49:44] <Lcvette> since i know it is setup so you can change things fairly globally
[13:49:57] <Lcvette> not the style just the format
[13:50:01] <JT[m]1> yea that's basicly what I'm doing too grab bits and pieces then delete the others
[13:50:11] <Lcvette> will return the style to your tastes
[13:51:14] <JT[m]1> those are not exacty what I want but close enough to get me rolling...
[13:51:53] * Lcvette uploaded an image: Screenshot_2019-03-23_13-51-40.png (51KB) < https://matrix.org >
[13:51:55] <JT[m]1> not sure how I want to layout the qss file with base widgets first or last... prob last and more finite selectors first
[13:52:17] <JT[m]1> you like them colors!
[13:52:17] <Lcvette> i like global first and finite last
[13:53:09] <JT[m]1> the double gradient on the blue buttons, what is the syntax for that?
[13:53:43] <Lcvette> its in probe basic
[13:53:47] <Lcvette> sec
[13:54:02] <roguish[m]> Lcvette: yeah, that's really good.
[13:54:48] <Lcvette> background: qlineargradient(spread:pad, x1:0, y1:0, x2:0, y2:1, stop:0 rgba(85, 85, 238, 255), stop:0.544974 rgba(90, 91, 239, 255), stop:1 rgba(126, 135, 243, 255));
[13:55:01] <Lcvette> lol.. thats probe basic
[13:55:23] <Lcvette> i have reverted the main buttons in unchecked state to the stock setting
[13:55:34] <Lcvette> haven't done the borders yet though
[13:55:48] <Lcvette> currently they areblack borfders so they don't show up
[13:56:10] <Lcvette> and thats bebas kai font
[13:57:24] <JT[m]1> thanks, I need to study a bit on qlineargradient
[13:57:38] <Lcvette> this is where using the designer is best JT
[13:57:45] <Lcvette> there is a gradient builder in it
[13:58:09] <Lcvette> i use it on a test button usually and it kicks out the code then when im happy i copy it to the qss
[13:58:13] <Lcvette> in the global
[13:58:23] <Lcvette> thats why i like that format
[13:59:16] * hazzy-m uploaded an image: IMG_20190323_135644433.jpg (97KB) < https://matrix.org >
[14:01:00] <JT[m]1> be back in a bit
[14:01:12] <JT[m]1> hazzy: monitor a bit short?
[14:01:36] <hazzy-m> Yep
[14:02:14] <hazzy-m> Rather screen a bit tall lol
[14:02:24] * hazzy-m uploaded an image: IMG_20190323_140145961.jpg (107KB) < https://matrix.org >
[14:02:32] <hazzy-m> Gay one fits perfectly
[14:06:30] <Lcvette> hazzy, which one is that?
[14:11:24] -!- pcw_home has quit [Ping timeout: 252 seconds]
[14:38:27] <Lcvette> JT: is the set coordinates system offsets qlabel anything special? or can i adjust it?
[14:39:30] <Lcvette> ie: is it just a regular QLabel for a text label?
[15:04:37] <JT[m]1> Lcvette: look at the top of the property editor it tells you what the widget is
[15:05:39] <Lcvette> I am just asking if its special
[15:05:48] <Lcvette> or can I nuke it and redo it?
[15:05:55] <Lcvette> its formatting is locked
[15:05:59] <Lcvette> not sure why
[15:06:28] <JT[m]1> hmm
[15:06:55] <Lcvette> it isn't responding to any font change commands
[15:06:59] <Lcvette> global or otherwise
[15:07:21] <Lcvette> wasn't sure if it was an embedded widget or something special i was unaware of
[15:07:34] <Lcvette> it just says Qlabel
[15:07:41] <Lcvette> so i didn't think it was
[15:07:44] <JT[m]1> Lcvette: find g5xWidget on the object inspector
[15:07:47] <Lcvette> but its acting wierd
[15:07:58] <JT[m]1> it has a stylesheet set
[15:08:30] <Lcvette> yup
[15:08:33] <Lcvette> that was it
[15:08:56] -!- pcw_home has joined #hazzy
[15:08:57] * JT[m]1 was new not know how lol
[15:10:48] <Lcvette> yeah your style sheet formatting was missing alot of identifiers
[15:11:16] <JT[m]1> don't need any if you do it in the widgets stylesheet
[15:11:18] <Lcvette> if you build them the same way you do the qss it makes it easier
[15:11:37] <JT[m]1> if you just use qss it's easier
[15:17:34] <JT[m]1> if you look most of the containers have some stylesheet stuff including the main window and IMHO all that needs to go away
[15:18:24] <JT[m]1> I'll probley do that in the morning, fixing to head to Farmington
[15:19:25] <JT[m]1> one thing is odd, my touch screen down here is 1280 x 768 but mill touch doesn't fit even with the tool bar hidden I only have half of the bottom row of buttons
[15:20:17] <JT[m]1> I think the mainwindow title is tacked on top of the mainwindow size
[15:23:08] <Lcvette> even if you go fullscreen mode?
[15:56:36] <hazzy-m> the dark2 style sheet fits on the screen fits perfect, the dark1 it too big for some reason
[15:57:41] <JT[m]1> fullscreen won't do anything cause some dummy set the mainwindow to fixed, but that same dummy just figured out how to turn the title bar off so it does not take up that extra space
[15:58:00] <JT[m]1> probley some margins made it grow
[15:58:51] <hazzy-m> just had a older chineese guy stop by to look at the car and shop, he started telling stories about working in the factories, realy fastinating. His specialy was maintaining the control systems for planers
[15:59:29] <hazzy-m> he said they were all tube based DC motor drives
[16:00:31] * JT[m]1 uploaded an image: Screenshot at 2019-03-23 15-00-00.png (41KB) < https://matrix.org >
[16:26:32] <Lcvette> JT: I like that color format JT!
[16:26:59] <Lcvette> its like an arctic
[16:31:32] * Lcvette uploaded an image: Screenshot_2019-03-23_16-31-19.png (55KB) < https://matrix.org >
[16:32:21] -!- biqut2 has quit [Remote host closed the connection]
[16:34:53] -!- biqut2 has joined #hazzy
[16:37:43] * JT[m]1 heads out, see you in the morning
[17:09:07] -!- biqut2 has quit [Quit: Leaving]
[17:28:29] -!- biqut2 has joined #hazzy
[17:55:02] <Lcvette> hazzy: you on
[17:55:16] <Lcvette> im getting my ass kicked by a couple buttons and can't figure out why
[18:39:19] * JT[m]1 is at 12 West
[18:39:38] <JT[m]1> Lcvette what's up?
[18:55:36] <Lcvette> i have no clue
[18:55:46] <Lcvette> i caved
[18:56:37] <Lcvette> formatting is perfect in designer, but when it opens in the gui, it blows right past the layout constraints
[18:57:27] <JT[m]1> I've seen that before
[18:58:22] <Lcvette> fixed it, but it should require what i did
[18:58:30] <JT[m]1> Is it changing the size
[18:58:59] <Lcvette> no just wasn't containing the formatting
[18:59:33] <JT[m]1> Weird
[18:59:41] <Lcvette> was allowing the one row of buttons to expand past the constrained margin limit
[18:59:46] <Lcvette> yeah very
[19:02:49] * Lcvette uploaded an image: Screenshot_2019-03-23_19-02-37.png (59KB) < https://matrix.org >
[19:03:20] * Lcvette uploaded an image: Screenshot_2019-03-23_19-03-06.png (58KB) < https://matrix.org >
[19:04:13] <Lcvette> JT: fixed the backplot formatting too
[19:09:22] <JT[m]1> Cool
[19:43:51] <biqut2> well I've done a fresh install, recompiled a preempt kernel, linuxcnc 2.8, and pip install git+https://github.com/kcjengr/qtpyvcp.git. still can't seem to get probe basic lathe to run. anyone want o point out my stupid mistake? http://dpaste.com
[20:29:20] * biqut2 is trying something different, be back
[20:29:33] -!- biqut2 has quit [Quit: Leaving]
[20:31:26] <Lcvette> lathe is not updated
[20:31:59] <Lcvette> and won't be until probe basic mill is 100%
[20:39:00] * Lcvette uploaded an image: Screenshot_2019-03-23_20-38-44.png (47KB) < https://matrix.org >
[20:39:22] * Lcvette uploaded an image: Screenshot_2019-03-23_20-39-12.png (53KB) < https://matrix.org >
[21:02:42] <JT[m]1> what did you fix on the backplot?
[21:02:54] * JT[m]1 is back to the chicken ranch
[21:08:25] <Lcvette> the buttons
[21:08:35] <Lcvette> they were stuffed into the tabs
[21:09:02] <Lcvette> i just added a widget box for them so i could create a layout and add a bottom margin
[21:24:51] <JT[m]1> I see what you mean, looks better with even spacing
[22:07:54] <Lcvette> Yeah. Helps