#hazzy | Logs for 2018-09-29

Back
[10:24:55] -!- Roguish has joined #hazzy
[14:32:44] -!- Roguish_ has joined #hazzy
[14:34:04] -!- Roguish has quit [Ping timeout: 250 seconds]
[14:34:09] Roguish_ is now known as Roguish
[14:38:47] -!- Roguish_ has joined #hazzy
[14:42:11] -!- Roguish has quit [Ping timeout: 252 seconds]
[14:42:12] Roguish_ is now known as Roguish
[18:45:01] <TurBoss> Hello
[19:29:25] <hazzy-m> hello
[19:29:51] <TurBoss> hey
[19:30:57] <TurBoss> what are you working on?
[19:32:15] <hazzy-m> other things
[19:32:23] <hazzy-m> need to get back on QtPyVCP
[19:33:20] <TurBoss> I'll try to do something for the widgets
[19:33:33] <TurBoss> do you hav some minutes to discuss that?
[19:33:35] <TurBoss> 2 o 3
[19:33:47] <TurBoss> **dialogs
[19:33:48] <hazzy-m> yes!
[19:34:21] <TurBoss> custom vcp doesn't use any discovery method?
[19:35:02] <hazzy-m> No, it doesn't, yet
[19:35:19] <TurBoss> do you have some ideas?
[19:35:27] <TurBoss> i was thinking on
[19:35:45] * TurBoss sent a long message: < https://matrix.org >
[19:35:54] <TurBoss> and check the output
[19:36:15] <hazzy-m> hmm, I guess that would work
[19:36:35] <TurBoss> ok I'll do that way for now---
[19:36:37] <TurBoss> :P
[19:36:46] <hazzy-m> how would you launch them though? You'd need to know the class as well as the module
[19:37:05] <TurBoss> a regular button linked to "Form"
[19:37:17] <TurBoss> hmmm
[19:37:30] <TurBoss> idea
[19:37:53] <TurBoss> isn't the parent accesible on widgets
[19:37:59] <hazzy-m> yes
[19:38:15] <TurBoss> and the parent of the parent
[19:39:14] <TurBoss> I'll try to get the root
[19:39:20] <TurBoss> ok that could work
[19:39:38] <TurBoss> but not sure how to add slots to the root
[19:39:50] <hazzy-m> You can get the rood window with: window = QApplication.instance().activeWindow()
[19:39:50] <TurBoss> root = parent master
[19:40:19] <TurBoss> but how can I add slots to the root
[19:40:43] <hazzy-m> I have an idea, we need app actions!
[19:40:47] <TurBoss> app actions?
[19:40:54] <hazzy-m> I'll play with it for a bit
[19:41:10] <hazzy-m> app actions like the machine actions etc.
[19:41:29] <TurBoss> sounds good
[19:41:56] <TurBoss> if you point me some direction i can draft something
[19:42:00] <TurBoss> if you are busy
[19:42:01] <hazzy-m> then you can do: `app.dialog.show:offsets_dialog` or something like that
[19:42:09] <TurBoss> hmmmmmmmmmmmmmm
[19:42:23] <TurBoss> that would be great
[19:42:44] <hazzy-m> and then use a regular action button or action menu item to launch it
[19:42:46] <hazzy-m> I'm on it!
[19:42:47] <hazzy-m> :)
[19:42:53] <TurBoss> oh thanks!
[19:55:08] <TurBoss> https://i.redditmedia.com
[20:26:57] <Not> [02QtPyVCP] 07TurBoss pushed 031 commit to 03offsets_dialog [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/d230b719c9c33d64e1853897c4621c6d48fed27e...60b87523e0fd9c65f027a68af87758d7e45c5592
[20:26:59] <Not> [02QtPyVCP] 07TurBoss 0360b8752 - better name for variable
[20:41:11] <TurBoss> hazzy: how is goin?
[20:53:58] <hazzy-m> very well
[21:00:33] <Lcvette> I'll build it!
[21:00:46] <hazzy-m> Hurray!
[21:00:46] <TurBoss> hello
[21:00:49] <hazzy-m> :D
[21:07:31] <hazzy-m> TurBoss: Almost have it!!
[21:07:51] <TurBoss> woaw
[21:08:14] <hazzy-m> it works!!
[21:08:17] <hazzy-m> Hurray!
[21:10:04] * hazzy-m posted a file: actions.mp4 (75KB) < https://matrix.org >
[21:11:41] <TurBoss> woahhh
[21:14:09] <Not> [02QtPyVCP] 07Kurt Jacobson created branch 03dialog_launcher
[21:14:41] <hazzy-m> the working launcher button is in brender
[21:14:51] <TurBoss> great
[21:14:52] <hazzy-m> still very crude, but a start
[21:19:23] <TurBoss> got this : http://dpaste.com
[21:19:28] <TurBoss> but working
[21:20:55] <Not> [02QtPyVCP] 07TurBoss pushed 031 commit to 03dialog_launcher [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/4dfd5c561f08456e123c4fdea8ffa2862bbfff93...b0a5d6148e3d1c9b671c6a3b43c777b3a85b98c1
[21:20:56] <Not> [02QtPyVCP] 07TurBoss 03b0a5d61 - typos
[21:21:34] <hazzy-m> Thanks, I'll fix that
[21:21:42] <TurBoss> thanks
[21:22:01] <hazzy-m> Is there any time the offset dialog should not be able to be shown?
[21:22:07] <hazzy-m> Like when the machine is running
[21:22:33] <TurBoss> at least disable "set" button
[21:22:44] <TurBoss> can be done in widget side?
[21:23:01] <hazzy-m> Ok, I think we should implement ok and bindOk methods for the dialogs
[21:23:15] <TurBoss> ?
[21:23:26] <hazzy-m> then any menu actions used to launch the dialog will also be disabled
[21:24:07] <TurBoss> ok
[21:24:36] <hazzy-m> Like these: https://gitlab.com
[21:25:52] <hazzy-m> This has a doc string: https://gitlab.com
[21:26:07] <TurBoss> ahhhh ok
[21:26:34] <hazzy-m> Not sure if that is a good way to do it, but it works :)
[21:26:45] <TurBoss> should be ok
[21:31:25] <TurBoss> hmmmmm
[21:31:33] <TurBoss> but
[21:31:45] <TurBoss> I issue md commands I should be checking if ok for mdi
[21:31:50] <TurBoss> *mdi
[21:32:17] <hazzy-m> yes, but that is easy
[21:32:31] <hazzy-m> if you use the `machine.issue_mdi` action
[21:32:53] <TurBoss> ahhh
[21:33:03] <TurBoss> I was using regular linuxcnc mdi
[21:33:09] <TurBoss> didn't notice about that
[21:33:20] <hazzy-m> sek, I'll show you how
[21:33:57] <TurBoss> oh fantastic
[21:35:37] * hazzy-m sent a long message: < https://matrix.org >
[21:37:25] <hazzy-m> also
[21:38:41] * hazzy-m sent a long message: < https://matrix.org >
[21:39:49] <TurBoss> oky thanks
[21:40:40] <hazzy-m> you can bind a widget so it is only enable when the action is ok by doing:
[21:41:20] <hazzy-m> ```python
[21:41:20] <hazzy-m> issue_mdi.bindOk(widget=myWidget)
[21:41:46] <TurBoss> woah
[21:41:53] <TurBoss> ok I'm with that
[21:43:14] <hazzy-m> I need to write some docs ...
[21:51:06] <TurBoss> hmmm
[21:51:43] <TurBoss> http://dpaste.com :|
[21:53:17] <hazzy-m> hmmm
[21:53:17] <TurBoss> I broke it
[21:53:36] <hazzy-m> is the id class attribute still there?
[21:55:05] <TurBoss> yes
[21:55:24] <TurBoss> I also tryed to add it to the other dialogs
[21:55:47] <hazzy-m> ok
[21:55:59] <hazzy-m> looking into it
[21:57:26] <TurBoss> is somthing I did
[21:57:48] <TurBoss> error from the widget are non show
[21:57:55] <TurBoss> :|
[21:58:22] <hazzy-m> can you push your changes?
[21:58:26] <TurBoss> yes
[21:58:57] <Not> [02QtPyVCP] 07TurBoss pushed 031 commit to 03dialog_launcher [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/b0a5d6148e3d1c9b671c6a3b43c777b3a85b98c1...1a0d09e958957766c512895b00934e4809b65da2
[21:58:58] <Not> [02QtPyVCP] 07TurBoss 031a0d09e - this break things :@
[21:59:01] <TurBoss> done
[21:59:21] <hazzy-m> checking
[22:00:46] <TurBoss> 😅
[22:00:58] <Lcvette> I'll break it!
[22:01:05] <hazzy-m> looks fine
[22:01:06] <hazzy-m> haha
[22:01:07] <Lcvette> What you want me to break?
[22:01:16] <TurBoss> I can do it myself :P
[22:01:27] <TurBoss> lol
[22:01:28] <Lcvette> 😂
[22:01:36] <hazzy-m> try to break the dialogs, you can only make them better :D
[22:01:57] <hazzy-m> lol
[22:01:59] <TurBoss> any idea?
[22:02:11] <hazzy-m> looks perfect
[22:02:23] <hazzy-m> I don't understand why it does not work
[22:02:32] <TurBoss> hay you tries locally?
[22:02:37] <TurBoss> got the error msgs?
[22:02:43] <hazzy-m> yes
[22:02:49] <TurBoss> they looks strange
[22:03:00] <Lcvette> I have no pi or I'd try
[22:03:32] <hazzy-m> all you need it apple pie
[22:04:17] <Lcvette> To night it was for raspi
[22:04:42] <Lcvette> See I know some lingo
[22:04:51] <hazzy-m> LOL, you do!
[22:04:55] <Lcvette> I thought*
[22:05:01] <hazzy-m> learning like a parrot
[22:05:04] <hazzy-m> xD
[22:05:08] <Lcvette> Up
[22:05:13] <Lcvette> Yup
[22:06:13] <TurBoss> hohoohoh
[22:06:32] <hazzy-m> LOL
[22:06:38] <hazzy-m> did you get it?
[22:06:47] <TurBoss> no 😠
[22:06:58] <hazzy-m> neither do I
[22:07:01] <hazzy-m> I have to run
[22:07:05] <hazzy-m> bbl
[22:07:08] <TurBoss> bye
[22:45:11] <Not> [02QtPyVCP] 07TurBoss pushed 031 commit to 03dialog_launcher [+0/-0/±1] 13https://gitlab.com/Hazzy/qtpyvcp/compare/1a0d09e958957766c512895b00934e4809b65da2...7eb287a27102fa7c41f2ffa587beb796d6dddd1e
[22:45:13] <Not> [02QtPyVCP] 07TurBoss 037eb287a - this works again