Brainstorm

@SGaist said in Licenses craziness!:

What happens usually is that developers use a different version of the database system that was used to build the Qt plugins hence the potential need to re-build the corresponding plugins.

This isn't an excuse because I don't face any problem when I use commercial products (as I mentioned before ex. Delphi). Do other companies make a magical solution for this issue?! Of course not.

If you want to avoid that, then you should maybe consider using ODBC. You have to take into account that many of the database system you are talking about have several versions supported in parallels with sometimes different features. Do you expect Qt to provide a pre-built plugin for each of these versions ?

Since I knew Qt I couldn't use any Qt plugin (specifically SQL plugins) by default because I always need to rebuild it from scratch (the old Qt binary distros didn't include binaries for SQL plugins except SQLite)

Because Qt can be used under LGPL/GPL doesn't mean its development is free nor that there are limitless hardware to build and produce the pre-built release nor thousands of developers working on it every day.

I understand your frustration regarding licenses but it looks like you don't realise the jungle that it is. Because a product is free it doesn't mean you can do whatever you want to with it.

This issue not related to open source version Qt, the commercial version of Qt has same problem!

Yeah, that was basically it. When I stitched together the examples from above, I neglected to notice that my worker object had two timers declared, and I wasn't consistent on which I used.

Works now. I've tested multiple starts and stops, and verified that the "finished" signal works, too. I do believe I have a functional example. I also modified the program so the worker passes the value to the widget for display.

So, to summarize what I've learned here:

run at least two threads: one for the UI and one to do work. This prevents compute-intensive tasks from blocking the UI updates. create a class for the worker, and instantiate an object in main(). use moveToThread to move the worker object to another thread. make your worker interrupt-driven (work depends mostly on signals from UI). use the arguments in the signal/slot routines to pass data.

I think I have a basis for reasonable design now. Thank you to everyone who participated in this.

@daeto
did you specify an absolute or relative lib path in the project's AdditionalLibraryDirectories property?
What libs did you add to the project's AdditionalDependencies property?
And what does the errors exactly say?

Not even aware of "Fluent Design" tech/product name is until seeing your post... still not really knowing.
What I can gather it's a Microsoft heavy gloss marketing attempt at 3d interface / Ui?

Have you seen:
https://blog.qt.io/blog/2017/05/24/qt3d/

@tekojo

Thank you for your detailed answer! This really helps me in the right direction! :D
Most things are around what I expected them to be, which is great.
I'll mark this thread as solved, thanks again for the help!

@Konstantin-Tokarev Thanks, I see it now.

https://softwareengineering.stackexchange.com/questions/312758/does-providing-object-files-satisfy-lgpl-relink-clause

@Konstantin-Tokarev that's exactly what I meant, thanks for the clarification.

@VRonin I guess there is actually no reason to test, if fglrx is deprecated, and Open Source drivers works fine, I just mark this topic as solved.

Hi,

From the top of my head, you can try to set alignment flag to Qt::AlignHCenter rather than 0.

@Drakkhan I should mention, that this resize in ResizeEvent can easily end in an recursive loop.
This should be pretty safe, if it is a standalone window for example. But if you have to be careful, if you want to use it in QLayout. Those tend to be difficult.

I would suggest either, subclassing and making your own QLayout Flow Layout Example or nesting your custom Widget inside an other one that is effected by the Layout, and handels the positioning of your custom -square- widget.

I prefer the 2nd option myself.

I'd avoid repeating the namespace name in sub-namespaces: Morph:MorphUtils vs Morph:Utils. The second is cleaner.

@tham Yea and really someone has to be interested enough in hacking your application to do it. That is ultimately pretty rare unless it gets really popular or is a security based app.

Other than either of those scenarios I'm betting nothing will ever happen to/with your encrypted password. :)

@Konstantin-Tokarev I am downloading it now! Thank you! The msys2 package works like a charm

Hi,

The Elastic Node Example from the Graphics View framework might give you some ideas to start from.

Hi,

Can you show the code you use to do what you described ?

Thank you all. The problem is solved I think. I up vote all answers to appreciate your help.

@hfrmobile
\o/
well if iw works and target is linux, and you mostly depend on this tool to turn it on, then
it might work ok.
Other reason is:

"iw is a new nl80211 based Linux CLI configuration utility for wireless devices. It supports all new drivers that have been added to the kernel recently. "

So it might not be easy to ask to turn it on if its via drivers.