If you want to use D3.js without rewriting it in other language, your first options are either to embed browser, or use QML. Sure you can also run JS code in plain QJSEngine and add your objects there, but that's going to be more work
Yes, I'm running the unmodified example code.
I start the application from Qt Creator. You are correct there are options to disable Gestures via command line parameters. But options to disable like "no-pan" or "no-pinch" or " no-swipe" must be explicitly set to disable them. Since I'm running from Qt Creator, I haven't set any of these options. Hence all three gestures are enabled.
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.
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?
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!
@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.
No, after pressing ctrl +s I worked for a little while and then power was cut. Thanks.
I also check that folder. There is My_First_Calculator with cpp extension but not any other extensions.
Maybe it's gone!
Hello, this is ProgramBase2 (I forgot my login credentials for my previous account) - sorry.
Can anyone help me out with this problem? I forgot to mention what I'm looking for.
Can anyone please direct me to a tutorial or a book that instructs how to achieve the goals I posted?
Please do not direct me to a existing code project, I am not interested in the finished product. I am interested in how the person got to the finished product.
Also, please do not direct me to a basic tutorial. I am looking for something advanced (maybe solemn done in Qt before). I've seen it work in other MDI programs, so I know it can be done.
Thanks again (I'll remember my credentials this time).
"1000x" thing may only be relevant for building scenes out of very many QWidgets. In this case QGraphicsView/QGraphicsScene may be orders of magnitude more efficient.
Yea I did make that assumption that he was building a complex scene since I have never had a performance issue with QPainter before, even in mildly complex scenes. Also 1000x was definitely hyperbole as it wouldn't realistically be anywhere near that. ;)