Re: [Interest] QtDesigner needs redesign.

2017-01-05 Thread Serge K via Interest
5 Jan 2017, 3:13 +03:00 от "Tony Rietwyk" : > >You need to thoroughly debug your widget in the application BEFORE you try to >load and use it in Designer. Exactly at first I've got plugin in application >working fine but in Designer it's image was corrupted. I thought it

Re: [Interest] QtDesigner needs redesign.

2017-01-05 Thread Serge K via Interest
I just didn't imagine that will take too much time. >Четверг, 5 января 2017, 10:53 +03:00 от André Somers : > >Hi, >While I agree that the current plugin system is not convenient, I don't get why you would spend a week with QDialogBox-debugging instead of

Re: [Interest] QtDesigner needs redesign.

2017-01-04 Thread André Somers
Hi, While I agree that the current plugin system is not convenient, I don't get why you would spend a week with QDialogBox-debugging instead of building your own Qt Designer in debug mode and run that in a debugger against plugins also build in debug mode? André Op 04/01/2017 om 15:32

Re: [Interest] QtDesigner needs redesign.

2017-01-04 Thread Tony Rietwyk
Hi Serge, I agree that it's painful not having a debug build of Qt Designer provided pre-built. It might make using custom widgets a bit easier. You need to thoroughly debug your widget in the application BEFORE you try to load and use it in Designer. If the widget relies on other

Re: [Interest] QtDesigner needs redesign.

2017-01-04 Thread Jean-Michaël Celerier
On Wed, Jan 4, 2017 at 11:58 AM, Viktor Engelmann wrote: > > Custom components in Qt are just QWidget derivates and they can be taken > from a designer plugin. This requires some extra code for making them > findable (+give them an icon and name etc.) and plugins are

Re: [Interest] QtDesigner needs redesign.

2017-01-04 Thread Viktor Engelmann
Am 02.01.2017 um 14:40 schrieb Shawn Rutledge: > I used it extensively in previous jobs, and my experience then was that it > worked well enough to use, and boosts productivity a lot compared to writing > all the widget-construction code by hand. It got even better with the > Creator

Re: [Interest] QtDesigner needs redesign.

2017-01-03 Thread André Pönitz
On Mon, Jan 02, 2017 at 01:40:51PM +, Shawn Rutledge wrote: > > > On 2 Jan 2017, at 14:15, Thiago Macieira > > wrote: > > > > On segunda-feira, 2 de janeiro de 2017 13:55:43 BRST Serge K via > > Interest wrote: > >> Is there anybody now creating NEW QtDesigner?

Re: [Interest] QtDesigner needs redesign.

2017-01-03 Thread Bob Hood
On 1/3/2017 10:26 AM, André Pönitz wrote: My *personal* approach is to use Desiner only to play around to get layout and resizing behaviour right, but re-do the actual implementation in code, either from scratch or based on uic output. Indeed, this is precisely how I use it in my workflow as

Re: [Interest] QtDesigner needs redesign.

2017-01-03 Thread André Pönitz
On Mon, Jan 02, 2017 at 01:55:43PM +0300, Serge K via Interest wrote: > I used QtCreator with older Qt versions. Now I use QtCreator 4.0.1 > with Qt5.6.1 but I cannot see major difference between it's QtDesigner > and old one. There is none. > Through years Designer remains the same with ugly >

Re: [Interest] QtDesigner needs redesign.

2017-01-02 Thread Shawn Rutledge
> On 2 Jan 2017, at 14:15, Thiago Macieira wrote: > > On segunda-feira, 2 de janeiro de 2017 13:55:43 BRST Serge K via Interest > wrote: >> Is there anybody now creating NEW QtDesigner? Are there at least plans for >> it? WHEN???!! > > No, no one is working on that,

Re: [Interest] QtDesigner needs redesign.

2017-01-02 Thread Thiago Macieira
On segunda-feira, 2 de janeiro de 2017 13:55:43 BRST Serge K via Interest wrote: > Is there anybody now creating NEW QtDesigner? Are there at least plans for > it? WHEN???!! No, no one is working on that, as far as I know. -- Thiago Macieira - thiago.macieira (AT) intel.com Software