Printable View
Does setting the QTimer interval to 0 help anyhow? I've been struggling with creating an idle event for a rendering loop and everytime I got a different problem. 4.8 fixed one problem I had before but now I'm facing another. Whenever I add my graphics window custom control to the form, the timer is no more triggered until I either resize or move the window. Should I go back to MFC and leave open-source buggy libraries? Come on, gimme a break!!!
Yes, the QTimer fires immediately when the program returns to the Qt event loop. Any slot attached to the timeout() signal gets run at that time.Quote:
Originally Posted by qtoptus
How about trying to help yourself. Sounds like your "rendering loop" is doing things the wrong way. We cannot guess the creative way you have achieved this effect with absolutely no information from you.Quote:
I've been struggling with creating an idle event for a rendering loop and everytime I got a different problem. 4.8 fixed one problem I had before but now I'm facing another. Whenever I add my graphics window custom control to the form, the timer is no more triggered until I either resize or move the window.
Yes... especially if all you are going to do is complain that a perfectly good programming framework does not meet your needs.Quote:
Should I go back to MFC and leave open-source buggy libraries?
http://www.bbc.co.uk/cbbc/shows/gimme-a-breakQuote:
Come on, gimme a break!!!
I cannot understand why sometimes it's taken personal...anyway
How? Example?Quote:
Sounds like your "rendering loop" is doing things the wrong way
Not always, not perfectly.Quote:
Yes, the QTimer fires immediately when the program returns to the Qt event loop. Any slot attached to the timeout() signal gets run at that time.
It sounds like Qt requires achieving stuff in a "creative" way in order to work.Quote:
We cannot guess the creative way you have achieved this effect with absolutely no information from you.
Cute!
qtimer works without needing to resize/move a window, so it suggests there is something wrong with your control that keeps the event queue from emptying - qtimer (0) fires when the event queue is empty.
you have not provided any code at all.
you only asked two questions in your op -
does setting timer to 0 help?
should you go back to mfc?
How do you expect us to answer with the information you have provided?
I wasn't taking anything personally. I was merely pointing out that the best way to get an answer to a question about doing X with Y is to provide some information about what X is, how you are trying to do X, what you expected to happen, what actually happens, and why you think that Y is at fault. X and Y apply to your problem and Qt just the same as they would to your problem and MFC, .Net, or Lisp. Simply stating that Y is broken and threatening to take your bat and ball and go home is not going to get you anywhere.Quote:
Originally Posted by qtoptus
There are many more ways to do something wrong or sub-optimally than I have had dinners. Amleto has one general mechanism by which your code can break things. How are we supposed to know how you are doing anything? You have yet to tell us anything about your code, your "rendering loop", and how you are achieving the unusual effects you describe... only that you think it is Qt's fault. Yes, they are unusual behaviours coming from your program, but only you seem to have them. They are a huge number of people, myself included, who have had no issues with zero QTimers. When we can see what you are doing then we could possibly tell you how to do it better.Quote:
How? Example?Quote:
Originally Posted by ChrisW67
Prove it. Provide an example of how it doesn't work [docs=QTimer.html#details]as documented[/qtimer].Quote:
Not always, not perfectly.Quote:
Originally Posted by ChrisW67
Programming in general has a creative element. Qt requires you to use Qt in the way it designed to be used. This is absolutely no different to MFC, .Net or any other programming tool or framework.Quote:
It sounds like Qt requires achieving stuff in a "creative" way in order to work.
Chris, it's in the docs that qtimer will silently discard timeout events/signals in some circumstances. I don't know if that is what the op was referring to or not.
Sometimes frustration of a problem puts the blame on the framework...
After investigating the problem, I could find that adding a graphics widgets has nothing to do with the timer not being triggered. It only happens when making the widget a Direct3D capable window.
I pass the window handle of the widget to Direct3D stuff which resides in a DLL.
Another finding, if it's an OpenGL window then it works fine. All I'm doing is a simple form using VS plugin and QtDesigner, add a class derived from widget to the form, and inside the form I have the QTimer. This timer also calls boost::chrono timer functions.
Ok now problem solved when setting the timer anything but 0. Setting it to 1 works fine...weird...
there is a fundamental difference in behaviour of qtimer when the timeout is changed from 0 to 1. Just because it works, doesn't mean the original problem now gone.Quote:
Originally Posted by qtoptus
It would really help if you shared some of your code. A good guess would be some routines in the d3d dll are screwing up something in regard to what Qt expects.