You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some time ago, Qt added a new signal/slot mechanism, which also applies to single shots. Thus, to check for the availability of simulation results, we used to have:
However, to have the "new" syntax results in only the beginning of some traces to be rendered (using our noble_1962_local.sedml and by pressing down the F9 key):
while everything works as expected using the "old" syntax (!!):
Not sure what the cause is (@dbrnz, any ideas?). I tried to create a small test case (so I could report the issue to the Qt guys, but to no avail). It's true that our use of QTimer::singleShot() here is somewhat special since it is effectively a loop that stops when there are no more simulation results or when the simulation is stopped by the user. So, although it ought to work no matter which syntax we use, we should clearly revert this particular instance of QTimer::singleShot(). (I checked the other instances of QTimer::singleShot() and they should be fine since they are not loops.)
The text was updated successfully, but these errors were encountered:
agarny
changed the title
Simulation Experiment view: some results may be not be plotted at all
Simulation Experiment view: some results may not be plotted at all
Apr 11, 2018
Reopening since the problem was definitely not with the syntax used for Qt::singleShot(), but with the fact that we were not properly handling the addition of a new run.
Some time ago, Qt added a new signal/slot mechanism, which also applies to single shots. Thus, to check for the availability of simulation results, we used to have:
which we then replaced with:
However, to have the "new" syntax results in only the beginning of some traces to be rendered (using our
noble_1962_local.sedml
and by pressing down theF9
key):while everything works as expected using the "old" syntax (!!):
Not sure what the cause is (@dbrnz, any ideas?). I tried to create a small test case (so I could report the issue to the Qt guys, but to no avail). It's true that our use of
QTimer::singleShot()
here is somewhat special since it is effectively a loop that stops when there are no more simulation results or when the simulation is stopped by the user. So, although it ought to work no matter which syntax we use, we should clearly revert this particular instance ofQTimer::singleShot()
. (I checked the other instances ofQTimer::singleShot()
and they should be fine since they are not loops.)The text was updated successfully, but these errors were encountered: