[Interest] QQuickView focus problem

Hi, I am having a problem getting a QML form with a text input to work properly when hosted by QQuickView. The problem is that the text input will only get the focus once. If the focus goes to another window on the desktop then clicking in the form does not return the focus to it. The issue i

Re: [Interest] Unified items in QListView icon mode

Do you have a minimum sample that reproduce the problem ? On 18 nov. 2013, at 21:31, Philipp Kursawe wrote: > Its a mixed problem I guess. When the items has to long label, the total size > of the item is increased (horizontally) to fit the label text. However, if > there is no icon attached t

Re: [Interest] Unified items in QListView icon mode

Its a mixed problem I guess. When the items has to long label, the total size of the item is increased (horizontally) to fit the label text. However, if there is no icon attached to the item (becuase the models decoration returns none) then the items text appears top aligned and not where the other

Re: [Interest] Unified items in QListView icon mode

On 18 nov. 2013, at 18:02, Philipp Kursawe wrote: > I wonder whats broken with the QListView. > I want it to display 64x64 icons and a label (which can be quite long). > What properties do I have to set so the listview renders the items (even the > ones without a Qt::Decoration role) correctly

[Interest] Qt Installer Framework - Adding custom generated file to the installation

I am very new to QtInstallerFramework but I have successfully created an installer for my project where I package a bunch of precompiled binaries so my developers do not have to build them. The convenience I would like to add to the installer is the ability to generate a simple text file with th

[Interest] Unified items in QListView icon mode

I wonder whats broken with the QListView. I want it to display 64x64 icons and a label (which can be quite long). What properties do I have to set so the listview renders the items (even the ones without a Qt::Decoration role) correctly in a 64x64 grid? _

Re: [Interest] Best practices for settings

Philipp Kursawe schreef op 18-11-2013 13:25: On Mon, Nov 18, 2013 at 12:45 PM, André Somers > wrote: I often see with OO programmers that they very quickly turn to subclassing to use a class they find useful. Somehow, encapsulation doesn't seem to g

Re: [Interest] Best practices for settings

> The mechanism to be notified would be different depending on where the settings are stored. E.g. if they are stored in a file, you could try using a QFileSystemWatcher (although I haven't tried that myself), but you still wouldn't know > which setting changed. (Although maybe QConfFileSettingsP

Re: [Interest] Best practices for settings

On Mon, Nov 18, 2013 at 12:45 PM, André Somers wrote: > I often see with OO programmers that they very quickly turn to > subclassing to use a class they find useful. Somehow, encapsulation > doesn't seem to get the same amount of attention as inheritance does. > Inheritance is not the tool to use

Re: [Interest] Best practices for settings

On 18 Nov 2013, at 12:33 PM, Philipp Kursawe wrote: > I am also currently struggling how to wire up changes to QSettings with the > lack of signals/slots. Some of my plugins depend on global app settings but > with QSettings its impossible for them to get notified about changes in > settings.

Re: [Interest] Best practices for settings

Or the best thing for Linux + QML - use Qt GSettings binding https://launchpad.net/gsettings-qt :) 2013/11/18 Mandeep Sandhu : > On Mon, Nov 18, 2013 at 5:24 PM, André Somers wrote: >> Tomasz Siekierda schreef op 17-11-2013 17:29: >>> The settings class is a Singleton, and all options are accesib

Re: [Interest] Best practices for settings

On Mon, Nov 18, 2013 at 5:24 PM, André Somers wrote: > Tomasz Siekierda schreef op 17-11-2013 17:29: >> The settings class is a Singleton, and all options are accesible >> through member variables (private + getters and setters, or public - >> if you prefer). Although I personally believe Singleto

Re: [Interest] Best practices for settings

Tomasz Siekierda schreef op 17-11-2013 17:29: > The settings class is a Singleton, and all options are accesible > through member variables (private + getters and setters, or public - > if you prefer). Although I personally believe Singletons are evil, > they can be useful - and this is one of t

Re: [Interest] Best practices for settings

On Mon, Nov 18, 2013 at 5:03 PM, Philipp Kursawe wrote: > I am also currently struggling how to wire up changes to QSettings with the > lack of signals/slots. Some of my plugins depend on global app settings but > with QSettings its impossible for them to get notified about changes in > settings.

Re: [Interest] Best practices for settings

Hi Tim, Tim Hoffmann schreef op 17-11-2013 14:53: > Hi all, > > Are there any best practices for working with QSettings in larger > projects with many settings? > > In particular: > - How do you efficiently synchronize settings with widgets in an options > dialog. > - How do you efficiently detect

Re: [Interest] Best practices for settings

Philipp Kursawe schreef op 18-11-2013 12:33: > I am also currently struggling how to wire up changes to QSettings > with the lack of signals/slots. Some of my plugins depend on global > app settings but with QSettings its impossible for them to get > notified about changes in settings. > I thoug

Re: [Interest] QtCreator and Ctrl+Shift bindings

On 18 Nov 2013, at 10:30 AM, Oleg Shalnev wrote: > Of course I turn of all Ctrl+Shift mappings in QtCreator but Creator still > wait for some key after Ctrl+Shift combination. Then you should probably file a bug. ___ Interest mailing list Interest@q

Re: [Interest] Best practices for settings

I am also currently struggling how to wire up changes to QSettings with the lack of signals/slots. Some of my plugins depend on global app settings but with QSettings its impossible for them to get notified about changes in settings. I thought subclassing QSettings is a good idea, until I found it

Re: [Interest] QtCreator and Ctrl+Shift bindings

Hi, On Sun, Nov 17, 2013 at 7:42 PM, Thiago Macieira wrote: > On domingo, 17 de novembro de 2013 20:24:31, Oleg Shalnev wrote: > > To tell the truth I don't understand why there is no reaction on thi > > message. > > May be this problem is not a problem, or it's not interesting to the > people >

Re: [Interest] QProgressDialog not showing & processEvents()

> I strongly object to using a thread for something this simple. Threading > is to be avoided whenever possible, because it's so hard to debug. Use There's no black magic involved in threads. Though I agree it might be an overkill in some cases, not so sure about this case. > the chunks method in

Re: [Interest] Best practices for settings

On 17 Nov 2013, at 2:53 PM, Tim Hoffmann wrote: > Hi all, > > Are there any best practices for working with QSettings in larger > projects with many settings? > > In particular: > - How do you efficiently synchronize settings with widgets in an options > dialog. > - How do you efficiently det

Re: [Interest] QProgressDialog not showing & processEvents()

Bo Thorsen schreef op 18-11-2013 9:27: > Den 18-11-2013 08:59, Mandeep Sandhu skrev: >>> You have two viable approaches here: >>> * break up the saving method into chunks. That is, do a small part of the >>> work of the saving, queue the next piece of work to be done, and return to >>> the eventloo

Re: [Interest] QtCreator and Ctrl+Shift bindings

On 14 Nov 2013, at 7:42 AM, Oleg Shalnev wrote: > Hello all. > > By default QtCreator use some Ctrl+Shift bindings, but Ctrl+Shift is one of > well known > and very popular keysequence for changing keyboard layout. > Even I remove all sequences with Ctrl+Shift in the beginning, after typing >

Re: [Interest] QProgressDialog not showing & processEvents()

Den 18-11-2013 08:59, Mandeep Sandhu skrev: >> You have two viable approaches here: >> * break up the saving method into chunks. That is, do a small part of the >> work of the saving, queue the next piece of work to be done, and return to >> the eventloop. The eventloop will then trigger the next q