@wasawi2 If you can locate maintenancetool.ini of your MaintenanceTool, try to delete it then repeat the solution that worked partially for you, see if it makes it update itself this time.

not sure how you handle your mqtt messages in qt code. Qt has a mqtt module and you may take a look at it.
I guess you may not need a timer. Instead, you create a signal with info when the message comes and connect that signal with any other qt qwidgets for update.
No check is needed as well.

Also, you can move the code that actually creates/adds the buttons to a separate class method and then call it from both the constructor and when you get a signal that new files were added. I am not sure what 'reloop constructor' means, but you do not want to try to call the constructor again.

I resolved it.

It because of RenderTarget.

I rollback it to default value.

@DanBar said in Problem with OpenSSL 1.1 after Qt update?:

If so, how can I make my application compatible with OpenSSL 1.1

It should be enough to just link to it during build and then make sure proper DLL files are in the same directory where your .exe is built. Which DLLs you need and what file names they are depends on compiler used and Open SSL version - sorry I don't remember them exactly, I use Windows only sporadically. If I recall correctly there used to be 2 DLLs in old versions, but nowadays it's a single file and it's called something like libssl-1_1-x64.dll.

or is there a way to switch back to OpenSSL 1.0 to test and see if this is the issue?

OpenSSL 1.0 has reached end of life a long time ago. DO NOT USE IT, it is a serious security risk at this point.

@mrjj okey

How did you do it now?

so for now I use this which seems to work...

xAxis->setRange(0,dat.size()); yAxis->setRange(*std::min_element(dat.constBegin(),dat.constEnd()),*std::max_element(dat.constBegin(),dat.constEnd()));

@aha_1980
well its not an easy tool to use.

I'm currently fighting with it as well, my antivirus pushes it into quarantine because it may be a potential virus.

Only happens with my own created tools not the QtCreator one.

I'm still trying to figure that one out...

And just to add to @mrjj, no Makefiles.

These kind of files should only exist in the build folder. If you have a duplicate in the project folder, it will drive you crazy.

Hi @UnitScan,

so please mark this topic as SOLVED too. Thanks!

@milan
Yes, it won't fail if dynamic linked so just check to understand why
it died running from creator.
Super. thank you for the feedback.

As I mentioned earlier I was pretty interested in this as nothing else with sufficiently good end-user experience exists in the Qt world. There is the Qt Installer Framework, but from what I've seen in Qt Creator, that is designed for developers - pulling people through wizards is not the way to go in 2017.

I've implemented DBLSQD in Mudlet, an open-source project (code available). We use DBLSQD handle the server-side part of running an updater - provide a feed clients can check for new versions, and parts of the client-side as well. On the client-side, it handles downloading of the new binaries, showing the update window, and a changelog window post-update.

Installing updates is complemented by Squirrel on Windows and since we use AppImage on Linux, no installation is necessary there. I did find it too difficult to integrate with Sparkle on macOS given by lack of Objective-C knowledge that Sparkle required, on macOS we use Sparkle entirely and DBLSQD provides the feed for Sparkle to work with.

So, overall, I'm super happy with this! Finally been able to add an updater to our application and @pentacent has been super helpful throughout the process. He's super responsive in communication, he adapted dblsqd to fit our needs, and he was also happy to include contributions we made to the clientside code. If I need an update solution for a commercial project, I would be more than happy to purchase a plan - the tech is good and support is top-notch.

https://en.wikipedia.org/wiki/Dependency_inversion_principle

Basically what you are doing is evil.

You should connect m_tree_view->selectionModel()'s currentIndexChanged() signal with a slot that calls setHeaderData in the model. that's all

@SGaist said in Problem with updating a widget:

oh fps was just to divide 1000 milliseconds by the ideal amount of times I wanted the program to refresh per second (fps), giving the interval at which the program should have been updated.

If you have SQL server why not just create a stored procedure in the server and call it in C++?! It's the best option under all circumstances.

If you can't use that then use a select then use something like:

bool alreadyExist = false; { QSqlQuery query; query.prepare("select * from MyTable where rowID=:rowID"); query.bindValue(":rowID",rowID); if(!query.exec()){ // select failed } alreadyExist = query.next(); } if(alreadyExist){ // update } else{ //insert }

@JKSH Thanks I will look into all the link you have provided and try to reach the concerned parties so that we can find a long term solution to this problem.

@jsulm thanks for the tipp!

I solved my problem by reinstalling VS2015 Update 2.

The workaround that appends a suffix to the requested image does the trick:

image.source = "image://images/myImage?id=" + Math.random()

but it's quite dirty. I wonder if there is a more elegant way (i.e. using signals) to keep the image source updated.