#pyqt | Logs for 2019-01-06
Back
[00:08:07] -!- mintograde has quit [Ping timeout: 258 seconds]
[00:21:21] <altendky> russw: so i did some work on that stuff the other day but didn't get it finished. came back today and started testing the last wheel and the pyqtdesigner didn't even work. so i go back to the '1.4' release and it doesn't work either. *sigh*
[00:21:25] <altendky> widget doesn't show up
[00:21:32] <altendky> such a pain
[01:46:16] <altendky> russw: alrighty, might have got it (of course mostly because of your efforts... thanks again). https://ci.appveyor.com
[01:47:25] <altendky> i think all i did was install, copy the pyqt5qmlwhatever.dll to the charts example directory then PS C:\Users\sda\desktop\pyqt5> .\venv3.7-64\scripts\pyqt5qmlscene.exe C:\Users\sda\Desktop\pyqt5\PyQt5_gpl-5.11.3\examples\quick\tutorials\extending\chapter6-plugins\app.qml -p C:\User
[01:47:25] <altendky> s\sda\Desktop\pyqt5\PyQt5_gpl-5.11.3\examples\quick\tutorials\extending\chapter6-plugins
[01:48:00] <altendky> i still get the pyqt5 has no attribute sip but it does show a window at least (with some pie chart slice thingies
[01:52:25] <altendky> if you'd like to help a little more... i could use 1) an example file that i can include and provide access to via --example-qml or whatever so users can easily verify it is working 2) a test file. for the designer plugin i made a test widget plugin that when loaded read an env var with a file path in it and wrote a word to that file. that way i could run designer, timeout in 10s or whatever, check the file and know the code
[01:52:25] <altendky> ran
[02:28:11] -!- kallesbar has joined #pyqt
[02:33:16] -!- mandeep has quit [Remote host closed the connection]
[02:38:42] -!- mandeep has joined #pyqt
[05:40:52] -!- BPL has joined #pyqt
[07:05:30] -!- anqxyr has joined #pyqt
[07:08:39] -!- Belxjander has quit [Quit: AmigaOSv4.1.6+//PowerPC native]
[07:09:07] -!- Belxjander has joined #pyqt
[07:32:44] -!- Belxjander has quit [Quit: AmigaOSv4.1.6+//PowerPC native]
[07:38:27] -!- Belxjander has joined #pyqt
[08:18:35] -!- mintograde has joined #pyqt
[09:44:49] -!- BPL has quit [Quit: Leaving]
[10:44:31] -!- jef has quit [Quit: Reconnecting]
[10:50:18] -!- jef has joined #pyqt
[13:58:16] -!- kallesbar has quit [Quit: Konversation terminated!]
[14:30:18] -!- anqxyr has quit [Ping timeout: 246 seconds]
[14:51:38] <altendky> i've got a QTreeView with a QstandardItemModel-inherited model. the modifications are for drag'n'drop methods where i implement my own handling entirely for the drop (return False from .dropMimeData()). a side affect of this seems to be that an other-than-desired item is highlighted after the drop operation is complete. i considered building the pile even bigger by handling the drop event on the view but i don't think
[14:51:38] <altendky> sufficient info is provided to know what to select
[14:52:06] <altendky> so the pile would have to be bigger bigger by the model storing what it last dropped so the view could query it while handling the event... ugh.
[14:53:26] <altendky> i guess the proper approach would be to try to eliminate my custom drop-handling code and let qt do as much as possible and just listen for the standard model telling me when it has deleted something?
[15:13:29] -!- necrose99 has joined #pyqt
[17:12:42] -!- rubenwardy has quit [Quit: Bye!]
[17:38:41] -!- necrose99 has quit [Read error: Connection reset by peer]
[22:11:12] -!- mintograde has quit [Ping timeout: 250 seconds]
[23:02:01] -!- mandeep has quit [Remote host closed the connection]