Brainstorm

@fcarney said in Another licensing question.:

Possibly even if using LGPL libs

Not if using shared libraries.

Hi and welcome to devnet,

In what way is it related to Qt ?

@Emrecp How about a variable or if statement in either mouse over/leave event that checks if the mouse is in the second widget?

@dracodraco if your issue is solved, please don't forget to mark your post as such!

@Kent-Dorfman thanks for that link. Turns out to be a surprisingly complicated subject, doesn't it? Particularly with the changes to C++ in 11 and 17 (per the article).

JonB's solution is simple, and seems to work, so I'm probably going to stick with it.

@J-Hilk That's interesting info, thanks. I'm using an external mouse, but the machine is indeed a Macbook with the trackpad set to clicking on a tap—so I guess it might be possible that Qt processes some low-level events in a weird way.

However, while I tried changing the system settings it turned out my MacOS forgot that it has a trackpad at all, and doesn't show those options even though input works fine. I don't think this new problem of mine is related to dragging-on-click since dragging-on-click is older IIRC (and occurs on Linux too, judging from the link)—but apparently I will now be fighting MacOS instead for a while, as quick googling didn't uncover anything on this topic. I also thought that I already checked if dragging-on-click persists with all input-tuning apps turned off, but perhaps I misremembered. Will report after I wrangle the OS and make it behave properly.

@Pooja-Bhusare
Well @LuGRU said:

You can achieve this by using libVLC or FFmpeg.

and @KoLiBer said that was so helpful.

@LeLev said in Translate texts read from a file:

Re-reading your requirements I guess you could be able to maintain (add/delete) your error strings without the need of recompiling the application.

My target machine has a list of possible errors to show to the user,

If those possible errors have a code (i.e. ABC123 or 123456) then you don't need the enum from @J-Hilk example, you'll use such codes as index for such std::array in the example or the key in the suggested map or whatever data structure you end up using.

In that way, you can maintain the .h file with the error strings separate from the source code, and just updating the .qm file(s) whenever the strings change. Since your source code will always use an index for the error string, no re-compilation of app is needed.

@SlySven you may want to watch BUG-76499 as the Qt developers are seeking to upgrade the API for cryptography.

@Asperamanca,

I would like to inform you that Aspose.Words for C++ is an advanced Word Document Processing API to perform a wide range of processing tasks. API provides document formatting, manipulation, mail merge, watermarking and much more capabilities directly within your own C++ applications without requiring Microsoft Word. API supports most of the Microsoft Word formats for processing. You can even integrate this native C++ API within your Qt application.

I am sharing here an example cmake project which uses Qt and Aspose.Words for C++. Then please do the following steps:

Download and install cmake Download and unpack Aspose.Words for C++ library Copy Aspose.Words.Cpp and CodePorting.Native.Cs2Cpp_vc14_20.3 folders next to CMakeLists.txt file Run the following command from command line: cd qthw cmake -G "Visual Studio 15 2017" -Thost=x64 -Ax64 -S . -B build -D"Qt5_DIR=<path-to-qt5>"

path-to-qt5 should be something like -x:\QT\5.14.2\msvc2017_64\lib\cmake\Qt5 - path to folder with Qt5Config.cmake file

It should create Visual Studio 2017 Solution with a proper setup for Qt and Aspose.Words for C++.

OK, thanks for the input, guys. I'll continue with my current method.

Thanks for the input, guys. Jon makes a good point about the need to convey this "hidden" feature to the user. That said, I might go ahead and try implementing this, simply because I can foresee a lot of good uses for the QKeyEvents. I can always go back and implement something that Jon could live with.

Thanks again...

EDIT: QKeyEvents aren't a great solution. It turns out that, on Windows and Linux (but not Mac), holding down keys prevents a button push from signalling. You have to press and release the keys, then push the button. Much clunkier than I'd hoped for.

Does it update in real time? If it does then what events happen on one should be sent to the other. Like @eyllanesc said, those would be the "instructions" of what to draw.

@mzimmers If i iterate over the interfaces like in your script, then it works with no problem :)
Running on windows :)

When using only the QHostAddress::Broadcast I get the wrong broadcast addr. I too think it is strange, but this is no issue for me, as it's always simple to determine the right address by code or manually :) just strange as you say :)

Anways, off to new issues :D

Thanks for the suggestions. I'm sure I'll have more questions about implementation, but as the original issue has been answered, I'm marking this as solved.

@JonB
Thanks a lot for your insight!

@EHSUN7B If you want to publish source code also then there is nothing special to consider.
If you do not want to deliver source code then use LGPL license for Qt and use Qt shared libraries.
When using static Qt libraries you have to be prepared to give the users the object files so they can relink the app against their own Qt libs.
Note: I'm not a lawyer.

@Konstantin-Tokarev
I think you're saying I'm wrong and then restating exactly what I wrote in the first place?

The default allocator reverts to the default heap manager and I'm well aware that it can be overriden, as I mentioned that as a potential strategy. so yes, it is implicit in the default STL.

Normally I stay well away from boost. Historically the lack of real boost documentation and frequently changing interfaces have left me severely jaded where boost is concerned. If/when something from boost finds its way into the standard then I'm more likely to give it a whirl, but I may take a look at their pool allocators. Thanks!

@aha_1980 Thank you for your kind reply and.... you are right, is not enough replace the name of the linked dll.