[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

2017-11-01 Thread Pearce Keesling
https://bugs.kde.org/show_bug.cgi?id=385341 Pearce Keesling <keesl...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RE

[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

2017-10-11 Thread Pearce Keesling
https://bugs.kde.org/show_bug.cgi?id=385341 --- Comment #2 from Pearce Keesling <keesl...@gmail.com> --- Something else I was wondering. Is there a particular reason that we're requiring argument names? As far as I can tell there is never really a place that those are needed from a devel

[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

2017-10-11 Thread Pearce Keesling
https://bugs.kde.org/show_bug.cgi?id=385341 --- Comment #1 from Pearce Keesling <keesl...@gmail.com> --- I've got most of the this solved. The only thing that's left as far as I can tell is the interface going back from rust String to a QString. I'll need to take a look at that when

[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

2017-10-03 Thread Pearce Keesling
https://bugs.kde.org/show_bug.cgi?id=385341 Pearce Keesling <keesl...@gmail.com> changed: What|Removed |Added CC||keesl...@gma