From R.Ziad at gmx.net Thu Sep 8 19:56:44 2016 From: R.Ziad at gmx.net (Rhouma Ziad) Date: Thu, 8 Sep 2016 19:56:44 +0200 Subject: [PySide] Create round corner with stylesheet does not work Message-ID: An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 1933 bytes Desc: not available URL: From R.Ziad at gmx.net Fri Sep 9 09:51:48 2016 From: R.Ziad at gmx.net (Rhouma Ziad) Date: Fri, 9 Sep 2016 09:51:48 +0200 Subject: [PySide] Create round corner with stylesheet Message-ID: An HTML attachment was scrubbed... URL: From frank at ohufx.com Mon Sep 19 07:04:26 2016 From: frank at ohufx.com (Frank Rueter | OHUfx) Date: Mon, 19 Sep 2016 17:04:26 +1200 Subject: [PySide] calling item.setData multiple times from inside QItemDelegate.setModelData Message-ID: <38a93cce-dfad-1167-f140-956b78c7d1ba@ohufx.com> Hi all, I'm using a QStandardItemModel with QItemDelegate for a custom view where I need to set multiple values for one item when the editor closes. I had these lines in my delegate's setModelData() method: item.setData(editor.player.isMirroredX , EL.MirrorXRole) item.setData(editor.player.isMirroredY , EL.MirrorYRole) item.setData(editor.player.currentFrameNumber() , EL.CurrentFrameRole) This led to inconsistent and unpredictable results though, e.g. often times the editor.player.currentFrameNumber() was not saved, or it was only saved when one of the other values changed as well. I had a hunch that the repeated emission of dataChanged was teh culprit, so blocked the model's signals before running the above three lines, then re-enabled the signals and manually emitted model.dataChanged once: # temporarily block model signals to prevent multiple emissions of # the dataChanged signal which causes unpredictable results item.model().blockSignals(True) # set values for allnecessary roles item.setData(editor.player.isMirroredX , EL.MirrorXRole) item.setData(editor.player.isMirroredY , EL.MirrorYRole) item.setData(editor.player.currentFrameNumber() , EL.CurrentFrameRole) # re-enable model's signla emissions item.model().blockSignals(False) # manually emit dataChanged once now that all roles have been changed item.model().dataChanged.emit(index, index) This seems somewhat hacky though, right? Is there a better way that people would recommend to set the value for multiple roles of the same index/item in one go inside the setModelData? Or is the above legit? Cheers, frank -- ohufxLogo 50x50 *vfx compositing | *workflow customisation and consulting * * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ohufxLogo_50x50.png Type: image/png Size: 2666 bytes Desc: not available URL: From frank at ohufx.com Mon Sep 19 08:56:24 2016 From: frank at ohufx.com (Frank Rueter | OHUfx) Date: Mon, 19 Sep 2016 18:56:24 +1200 Subject: [PySide] QListView: drag&drop custom item In-Reply-To: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> References: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> Message-ID: <353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> Anybody? I'm still struggling with this. I went back to using a QStandardItem for a while which solved the dag&drop behaviour, but now I really need to use a custom item that inherits QStandardItem which breaks the drop behaviour again. Any ideas or guidance would be greatly appreciated. Cheers, frank On 16/08/16 7:26 PM, Frank Rueter | OHUfx wrote: > Hi, > > I am trying to get drag&drop to work between two QListViews using a > custom item. > I can't find the info I need online other than this document > which helped a > little bit but now I'm stuck. > > Drag&drop from one QListView to another works fine when I use a > QStandardItem to hold my data, but when I use a custom item I run into > trouble, because the receiving model/view creates a QStandardItem when > the incoming custom items are dropped. > > Ideally I could tell the receiving model to use my custom item as the > default item and otherwise just do it's thing, but I suppose it won't > be that easy?! > I have played around with the receiving model's dropMimeData() and > insertRows() methods but can't work out how to read the incoming data > to then insert a custom item into the receiving model manually. > In QAbstractItemModel.dropMimeData() I tried reading > mimeData.data('application/x-qabstractitemmodeldatalist'), but that > returns a byte stream that I don't know how to handle. > > Do I have to re-implement the sender's drag data as well to send the > custom item in the first place? > > It seems that everything works out of the box except the creation of > the QStandardItem upon drop, rather than my custom item, so I am > hoping I don't have to re-invent the (drag&drop) wheel just to get > that one part right?! > > Any advise would be greatly appreciated. > > Thanks, > frank > > > > -- > ohufxLogo 50x50 *vfx compositing > | *workflow customisation > and consulting * * > > > > _______________________________________________ > PySide mailing list > PySide at qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 2666 bytes Desc: not available URL: From jukka.purma at aalto.fi Mon Sep 19 09:31:38 2016 From: jukka.purma at aalto.fi (Purma Jukka) Date: Mon, 19 Sep 2016 07:31:38 +0000 Subject: [PySide] QListView: drag&drop custom item In-Reply-To: <10318_1474268250_57DF8C5A_10318_3680_1_353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> References: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> <10318_1474268250_57DF8C5A_10318_3680_1_353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> Message-ID: Hi, since you asked any ideas... In my app I have had to re-invent drag&drop for some items (because I want to drag QGraphicsItems in scene while having all kinds of effects on the items they are connected while keeping the main event loop running etc. ) and learned a habit to give up when I didn’t find Qt-way of doing things and instead to choose the simplest pythonesque way. So in your case at this point, I would have 1. 'start drag' store the dragged data, just the main payload, not the Q-item containing them, in some stable object (main window), just as ’main.dragged_object’. 2. when drag gets dropped to those problem recipients, in drop event, manually put the data from main window into recipient, without bothering with the Q-representations of the data. In my app I have a multipurpose controller-object and ctrl.dragged is used to store the non-qt data of whatever is being dragged. It was my solution to struggle with QStandardItems and such. In conclusion, since we are doing things with Python + Qt, I think we are justified to skip Qt when there is an easier (or more readable) pythonesque way of doing things. Jukka > Frank Rueter | OHUfx kirjoitti 19.9.2016 kello 9.56: > > Anybody? > I'm still struggling with this. I went back to using a QStandardItem for a while which solved the dag&drop behaviour, but now I really need to use a custom item that inherits QStandardItem which breaks the drop behaviour again. > > Any ideas or guidance would be greatly appreciated. > > Cheers, > frank > > > On 16/08/16 7:26 PM, Frank Rueter | OHUfx wrote: >> Hi, >> >> I am trying to get drag&drop to work between two QListViews using a custom item. >> I can't find the info I need online other than this document which helped a little bit but now I'm stuck. >> >> Drag&drop from one QListView to another works fine when I use a QStandardItem to hold my data, but when I use a custom item I run into trouble, because the receiving model/view creates a QStandardItem when the incoming custom items are dropped. >> >> Ideally I could tell the receiving model to use my custom item as the default item and otherwise just do it's thing, but I suppose it won't be that easy?! >> I have played around with the receiving model's dropMimeData() and insertRows() methods but can't work out how to read the incoming data to then insert a custom item into the receiving model manually. >> In QAbstractItemModel.dropMimeData() I tried reading mimeData.data('application/x-qabstractitemmodeldatalist'), but that returns a byte stream that I don't know how to handle. >> >> Do I have to re-implement the sender's drag data as well to send the custom item in the first place? >> >> It seems that everything works out of the box except the creation of the QStandardItem upon drop, rather than my custom item, so I am hoping I don't have to re-invent the (drag&drop) wheel just to get that one part right?! >> >> Any advise would be greatly appreciated. >> >> Thanks, >> frank >> >> >> >> -- >> vfx compositing | workflow customisation and consulting >> >> _______________________________________________ >> PySide mailing list >> >> PySide at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/pyside > > _______________________________________________ > PySide mailing list > PySide at qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside From frank at ohufx.com Mon Sep 19 09:51:43 2016 From: frank at ohufx.com (Frank Rueter | OHUfx) Date: Mon, 19 Sep 2016 19:51:43 +1200 Subject: [PySide] QListView: drag&drop custom item In-Reply-To: References: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> <10318_1474268250_57DF8C5A_10318_3680_1_353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> Message-ID: <853d851d-b5c1-e78b-9e17-97a0c29b168a@ohufx.com> Thanks Jukka, that's probably not a bad idea considering how much time I have spent trying to get this to work via QT. I had been toying with the idea of just sending a dictionary of the relevant data, probably via a custom mime type, then re-creating the custom item upon drop in the receiving view. I will keep that in mind as my last resort, but it feels like the default implementation of the drop behaviour is soooo close, that it should be possible to drop a custom item in some QT-ish way without re-invening the wheel - or is that too optimistic? Here is a simple test code, hopefully we can get some more input with that: http://pastebin.com/5UDPQFjh With this code, when dropping an item fro the left into the right view, the print statement shows that a QStandardItem is produced rather than the custom item. Any more takers? Cheers, frank On 19/09/16 7:31 PM, Purma Jukka wrote: > Hi, > since you asked any ideas... In my app I have had to re-invent drag&drop for some items (because I want to drag QGraphicsItems in scene while having all kinds of effects on the items they are connected while keeping the main event loop running etc. ) and learned a habit to give up when I didn’t find Qt-way of doing things and instead to choose the simplest pythonesque way. > > So in your case at this point, I would have > 1. 'start drag' store the dragged data, just the main payload, not the Q-item containing them, in some stable object (main window), just as ’main.dragged_object’. > 2. when drag gets dropped to those problem recipients, in drop event, manually put the data from main window into recipient, without bothering with the Q-representations of the data. > > In my app I have a multipurpose controller-object and ctrl.dragged is used to store the non-qt data of whatever is being dragged. It was my solution to struggle with QStandardItems and such. > > In conclusion, since we are doing things with Python + Qt, I think we are justified to skip Qt when there is an easier (or more readable) pythonesque way of doing things. > > Jukka > >> Frank Rueter | OHUfx kirjoitti 19.9.2016 kello 9.56: >> >> Anybody? >> I'm still struggling with this. I went back to using a QStandardItem for a while which solved the dag&drop behaviour, but now I really need to use a custom item that inherits QStandardItem which breaks the drop behaviour again. >> >> Any ideas or guidance would be greatly appreciated. >> >> Cheers, >> frank >> >> >> On 16/08/16 7:26 PM, Frank Rueter | OHUfx wrote: >>> Hi, >>> >>> I am trying to get drag&drop to work between two QListViews using a custom item. >>> I can't find the info I need online other than this document which helped a little bit but now I'm stuck. >>> >>> Drag&drop from one QListView to another works fine when I use a QStandardItem to hold my data, but when I use a custom item I run into trouble, because the receiving model/view creates a QStandardItem when the incoming custom items are dropped. >>> >>> Ideally I could tell the receiving model to use my custom item as the default item and otherwise just do it's thing, but I suppose it won't be that easy?! >>> I have played around with the receiving model's dropMimeData() and insertRows() methods but can't work out how to read the incoming data to then insert a custom item into the receiving model manually. >>> In QAbstractItemModel.dropMimeData() I tried reading mimeData.data('application/x-qabstractitemmodeldatalist'), but that returns a byte stream that I don't know how to handle. >>> >>> Do I have to re-implement the sender's drag data as well to send the custom item in the first place? >>> >>> It seems that everything works out of the box except the creation of the QStandardItem upon drop, rather than my custom item, so I am hoping I don't have to re-invent the (drag&drop) wheel just to get that one part right?! >>> >>> Any advise would be greatly appreciated. >>> >>> Thanks, >>> frank >>> >>> >>> >>> -- >>> vfx compositing | workflow customisation and consulting >>> >>> _______________________________________________ >>> PySide mailing list >>> >>> PySide at qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/pyside >> _______________________________________________ >> PySide mailing list >> PySide at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/pyside From frank at ohufx.com Mon Sep 19 10:47:59 2016 From: frank at ohufx.com (Frank Rueter | OHUfx) Date: Mon, 19 Sep 2016 20:47:59 +1200 Subject: [PySide] QListView: drag&drop custom item In-Reply-To: <853d851d-b5c1-e78b-9e17-97a0c29b168a@ohufx.com> References: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> <10318_1474268250_57DF8C5A_10318_3680_1_353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> <853d851d-b5c1-e78b-9e17-97a0c29b168a@ohufx.com> Message-ID: <211f7144-b8f3-ba54-806f-81dae4f9acf5@ohufx.com> And one more follow up before I give up for the day: I found some code online that decodes the byte stream returned by a QDropEvent.mimeData().data() method so I get the item instance back. I worked that function into my example but the model refuses to append the dropped item. A new instance of my custom item inside the drop event appends just fine, but not the actual dropped item or a copy of it. I just can't see what's wrong with this. Can somebody please have a look? http://pastebin.com/UWWGXfNQ If this fails I guess I will have to create a new item on the fly and make sure to copy all relevant data across, though that seems unnecessary and error prone. Cheers, frank On 19/09/16 7:51 PM, Frank Rueter | OHUfx wrote: > Thanks Jukka, > > that's probably not a bad idea considering how much time I have spent > trying to get this to work via QT. > I had been toying with the idea of just sending a dictionary of the > relevant data, probably via a custom mime type, then re-creating the > custom item upon drop in the receiving view. > I will keep that in mind as my last resort, but it feels like the > default implementation of the drop behaviour is soooo close, that it > should be possible to drop a custom item in some QT-ish way without > re-invening the wheel - or is that too optimistic? > > Here is a simple test code, hopefully we can get some more input with > that: > http://pastebin.com/5UDPQFjh > > With this code, when dropping an item fro the left into the right > view, the print statement shows that a QStandardItem is produced > rather than the custom item. > > Any more takers? > > Cheers, > frank > > On 19/09/16 7:31 PM, Purma Jukka wrote: >> Hi, >> since you asked any ideas... In my app I have had to re-invent >> drag&drop for some items (because I want to drag QGraphicsItems in >> scene while having all kinds of effects on the items they are >> connected while keeping the main event loop running etc. ) and >> learned a habit to give up when I didn’t find Qt-way of doing things >> and instead to choose the simplest pythonesque way. >> >> So in your case at this point, I would have >> 1. 'start drag' store the dragged data, just the main payload, not >> the Q-item containing them, in some stable object (main window), just >> as ’main.dragged_object’. >> 2. when drag gets dropped to those problem recipients, in drop event, >> manually put the data from main window into recipient, without >> bothering with the Q-representations of the data. >> >> In my app I have a multipurpose controller-object and ctrl.dragged is >> used to store the non-qt data of whatever is being dragged. It was my >> solution to struggle with QStandardItems and such. >> >> In conclusion, since we are doing things with Python + Qt, I think we >> are justified to skip Qt when there is an easier (or more readable) >> pythonesque way of doing things. >> >> Jukka >> >>> Frank Rueter | OHUfx kirjoitti 19.9.2016 kello 9.56: >>> >>> Anybody? >>> I'm still struggling with this. I went back to using a QStandardItem >>> for a while which solved the dag&drop behaviour, but now I really >>> need to use a custom item that inherits QStandardItem which breaks >>> the drop behaviour again. >>> >>> Any ideas or guidance would be greatly appreciated. >>> >>> Cheers, >>> frank >>> >>> >>> On 16/08/16 7:26 PM, Frank Rueter | OHUfx wrote: >>>> Hi, >>>> >>>> I am trying to get drag&drop to work between two QListViews using a >>>> custom item. >>>> I can't find the info I need online other than this document which >>>> helped a little bit but now I'm stuck. >>>> >>>> Drag&drop from one QListView to another works fine when I use a >>>> QStandardItem to hold my data, but when I use a custom item I run >>>> into trouble, because the receiving model/view creates a >>>> QStandardItem when the incoming custom items are dropped. >>>> >>>> Ideally I could tell the receiving model to use my custom item as >>>> the default item and otherwise just do it's thing, but I suppose it >>>> won't be that easy?! >>>> I have played around with the receiving model's dropMimeData() and >>>> insertRows() methods but can't work out how to read the incoming >>>> data to then insert a custom item into the receiving model manually. >>>> In QAbstractItemModel.dropMimeData() I tried reading >>>> mimeData.data('application/x-qabstractitemmodeldatalist'), but that >>>> returns a byte stream that I don't know how to handle. >>>> >>>> Do I have to re-implement the sender's drag data as well to send >>>> the custom item in the first place? >>>> >>>> It seems that everything works out of the box except the creation >>>> of the QStandardItem upon drop, rather than my custom item, so I am >>>> hoping I don't have to re-invent the (drag&drop) wheel just to get >>>> that one part right?! >>>> >>>> Any advise would be greatly appreciated. >>>> >>>> Thanks, >>>> frank >>>> >>>> >>>> >>>> -- >>>> vfx compositing | workflow customisation >>>> and consulting >>>> >>>> _______________________________________________ >>>> PySide mailing list >>>> >>>> PySide at qt-project.org >>>> http://lists.qt-project.org/mailman/listinfo/pyside >>> _______________________________________________ >>> PySide mailing list >>> PySide at qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/pyside > > _______________________________________________ > PySide mailing list > PySide at qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside From frank at ohufx.com Wed Sep 21 03:44:47 2016 From: frank at ohufx.com (Frank Rueter | OHUfx) Date: Wed, 21 Sep 2016 13:44:47 +1200 Subject: [PySide] QListView: drag&drop custom item In-Reply-To: <211f7144-b8f3-ba54-806f-81dae4f9acf5@ohufx.com> References: <0c9ef571-4c98-a901-c158-f06f02865634@ohufx.com> <10318_1474268250_57DF8C5A_10318_3680_1_353431a0-53e4-84b8-c056-df3f26e1bb8d@ohufx.com> <853d851d-b5c1-e78b-9e17-97a0c29b168a@ohufx.com> <211f7144-b8f3-ba54-806f-81dae4f9acf5@ohufx.com> Message-ID: In case somebody else is interested, turns out that I can simply use setItemPrototype() on the receiving model to make it use my custom item whenever necessary. This should do away with all the other manual handling of dropped items, mime data etc. Cheers, frank On 09/19/2016 08:47 PM, Frank Rueter | OHUfx wrote: > And one more follow up before I give up for the day: > I found some code online that decodes the byte stream returned by a > QDropEvent.mimeData().data() method so I get the item instance back. > I worked that function into my example but the model refuses to append > the dropped item. > A new instance of my custom item inside the drop event appends just > fine, but not the actual dropped item or a copy of it. I just can't > see what's wrong with this. Can somebody please have a look? > http://pastebin.com/UWWGXfNQ > > If this fails I guess I will have to create a new item on the fly and > make sure to copy all relevant data across, though that seems > unnecessary and error prone. > > Cheers, > frank > > > On 19/09/16 7:51 PM, Frank Rueter | OHUfx wrote: >> Thanks Jukka, >> >> that's probably not a bad idea considering how much time I have spent >> trying to get this to work via QT. >> I had been toying with the idea of just sending a dictionary of the >> relevant data, probably via a custom mime type, then re-creating the >> custom item upon drop in the receiving view. >> I will keep that in mind as my last resort, but it feels like the >> default implementation of the drop behaviour is soooo close, that it >> should be possible to drop a custom item in some QT-ish way without >> re-invening the wheel - or is that too optimistic? >> >> Here is a simple test code, hopefully we can get some more input with >> that: >> http://pastebin.com/5UDPQFjh >> >> With this code, when dropping an item fro the left into the right >> view, the print statement shows that a QStandardItem is produced >> rather than the custom item. >> >> Any more takers? >> >> Cheers, >> frank >> >> On 19/09/16 7:31 PM, Purma Jukka wrote: >>> Hi, >>> since you asked any ideas... In my app I have had to re-invent >>> drag&drop for some items (because I want to drag QGraphicsItems in >>> scene while having all kinds of effects on the items they are >>> connected while keeping the main event loop running etc. ) and >>> learned a habit to give up when I didn’t find Qt-way of doing things >>> and instead to choose the simplest pythonesque way. >>> >>> So in your case at this point, I would have >>> 1. 'start drag' store the dragged data, just the main payload, not >>> the Q-item containing them, in some stable object (main window), >>> just as ’main.dragged_object’. >>> 2. when drag gets dropped to those problem recipients, in drop >>> event, manually put the data from main window into recipient, >>> without bothering with the Q-representations of the data. >>> >>> In my app I have a multipurpose controller-object and ctrl.dragged >>> is used to store the non-qt data of whatever is being dragged. It >>> was my solution to struggle with QStandardItems and such. >>> >>> In conclusion, since we are doing things with Python + Qt, I think >>> we are justified to skip Qt when there is an easier (or more >>> readable) pythonesque way of doing things. >>> >>> Jukka >>> >>>> Frank Rueter | OHUfx kirjoitti 19.9.2016 kello 9.56: >>>> >>>> Anybody? >>>> I'm still struggling with this. I went back to using a >>>> QStandardItem for a while which solved the dag&drop behaviour, but >>>> now I really need to use a custom item that inherits QStandardItem >>>> which breaks the drop behaviour again. >>>> >>>> Any ideas or guidance would be greatly appreciated. >>>> >>>> Cheers, >>>> frank >>>> >>>> >>>> On 16/08/16 7:26 PM, Frank Rueter | OHUfx wrote: >>>>> Hi, >>>>> >>>>> I am trying to get drag&drop to work between two QListViews using >>>>> a custom item. >>>>> I can't find the info I need online other than this document which >>>>> helped a little bit but now I'm stuck. >>>>> >>>>> Drag&drop from one QListView to another works fine when I use a >>>>> QStandardItem to hold my data, but when I use a custom item I run >>>>> into trouble, because the receiving model/view creates a >>>>> QStandardItem when the incoming custom items are dropped. >>>>> >>>>> Ideally I could tell the receiving model to use my custom item as >>>>> the default item and otherwise just do it's thing, but I suppose >>>>> it won't be that easy?! >>>>> I have played around with the receiving model's dropMimeData() and >>>>> insertRows() methods but can't work out how to read the incoming >>>>> data to then insert a custom item into the receiving model manually. >>>>> In QAbstractItemModel.dropMimeData() I tried reading >>>>> mimeData.data('application/x-qabstractitemmodeldatalist'), but >>>>> that returns a byte stream that I don't know how to handle. >>>>> >>>>> Do I have to re-implement the sender's drag data as well to send >>>>> the custom item in the first place? >>>>> >>>>> It seems that everything works out of the box except the creation >>>>> of the QStandardItem upon drop, rather than my custom item, so I >>>>> am hoping I don't have to re-invent the (drag&drop) wheel just to >>>>> get that one part right?! >>>>> >>>>> Any advise would be greatly appreciated. >>>>> >>>>> Thanks, >>>>> frank >>>>> >>>>> >>>>> >>>>> -- >>>>> vfx compositing | workflow customisation >>>>> and consulting >>>>> >>>>> _______________________________________________ >>>>> PySide mailing list >>>>> >>>>> PySide at qt-project.org >>>>> http://lists.qt-project.org/mailman/listinfo/pyside >>>> _______________________________________________ >>>> PySide mailing list >>>> PySide at qt-project.org >>>> http://lists.qt-project.org/mailman/listinfo/pyside >> >> _______________________________________________ >> PySide mailing list >> PySide at qt-project.org >> http://lists.qt-project.org/mailman/listinfo/pyside > > _______________________________________________ > PySide mailing list > PySide at qt-project.org > http://lists.qt-project.org/mailman/listinfo/pyside From alex.v.odesk at gmail.com Thu Sep 22 13:41:24 2016 From: alex.v.odesk at gmail.com (Alex V.) Date: Thu, 22 Sep 2016 11:41:24 -0000 Subject: [PySide] Connecting signal makes app exit. Message-ID: <57E3C31D.4040007@gmail.com> When I connect to selectionChanged signal, app silently exits (Linux). If I assign selectionModel to local variable before connecting, it works as supposed. Code below should stop executing at "connect", and should display window after uncommenting "sm = " I would like to know why it works this way. import sys, os from PySide.QtGui import * from PySide.QtCore import * if __name__ == "__main__": app = QApplication(sys.argv) wnd = QDialog() vbox = QVBoxLayout(wnd) qtr = QTreeWidget(wnd) vbox.addWidget(qtr) #sm = qtr.selectionModel() qtr.selectionModel().selectionChanged.connect(lambda *args: args) wnd.show() sys.exit(app.exec_()) From dan.malone at dreamworks.com Tue Sep 27 23:25:51 2016 From: dan.malone at dreamworks.com (Dan Malone) Date: Tue, 27 Sep 2016 21:25:51 -0000 Subject: [PySide] Shiboken license? Message-ID: I'm trying to wrangle approval on our usage of Shiboken, which hinges completely on which license it's under. Looking through all of the info, I find conflicting references to both LGPL and GPL. Our approval caveats that come with those have some critical differences so I really need to find out which is correct and I'm hoping someone on your end can help. Thanks, *Dan Malone* Software Coordinator DreamWorks Animation Tel. (818) 695-3869 email: dan.malone at dreamworks.com -------------- next part -------------- An HTML attachment was scrubbed... URL: