SimulationController don't works

Bug #411572 reported by Sergei Dorofeenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Yade
Fix Released
Undecided
Václav Šmilauer

Bug Description

For some reason SimulationController's buttons (play, pause, etc.) are disabled in the svn1934 and the indicator panel (with simulation time, etc.) is lacking (see attached figure). In addition, when SimulationController is actived SimulationView is updated only when you click the mouse on it (if the SimulationController is closed, then everything is fine).

Revision history for this message
Sergei Dorofeenko (sergei.dorofeenko) wrote :
Revision history for this message
Anton Gladky (gladky-anton) wrote : Re: [Bug 411572] Re: SimulationController don't works

I have just checked SVN 1935 and it works ok for me. All buttons are active.
______________________________
[ENG] Best Regards
[GER] Mit freundlichen Grüßen
[RUS] С наилучшими пожеланиями
[UKR] З найкращими побажаннями

Anton Gladkyy

2009/8/10 Sergei Dorofeenko <email address hidden>

>
> ** Attachment added: "Simulation Controller.png"
> http://launchpadlibrarian.net/30122175/Simulation%20Controller.png
>
> --
> SimulationController don't works
> https://bugs.launchpad.net/bugs/411572
> You received this bug notification because you are subscribed to Yade.
>
> Status in Yet Another Dynamic Engine: New
>
> Bug description:
> For some reason SimulationController's buttons (play, pause, etc.) are
> disabled in the svn1934 and the indicator panel (with simulation time, etc.)
> is lacking (see attached figure). In addition, when SimulationController is
> actived SimulationView is updated only when you click the mouse on it (if
> the SimulationController is closed, then everything is fine).
>

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

I added lock to omega that makes the buttons inactive during loading simulation (the "[loading]" instead of file name) to avoid crashes, last week.

How do you make it behave in the way as on the figure? It is a bug, yes.

Changed in yade:
status: New → Confirmed
Changed in yade:
assignee: nobody → Václav Šmilauer (eudoxos)
milestone: none → 0.20-0
Revision history for this message
Sergei Dorofeenko (sergei.dorofeenko) wrote :

Nothing special. Just click on Controller button or type yade.qt.Controller() in the console.

ps. May be important that I use a patch to gui/qt3/GLViewer.cpp because without it Viewer is not works (only black window).

===================================================================
--- gui/qt3/GLViewer.cpp (revision 1934)
+++ gui/qt3/GLViewer.cpp (working copy)
@@ -46,17 +46,17 @@
 void GLViewer::paintGL(void){
  /* paintGL encapsulated preDraw, draw and postDraw within QGLViewer. If the mutex cannot be locked,
   * we just return without repainting */
- #if BOOST_VERSION<103500
- boost::try_mutex::scoped_try_lock lock(Omega::instance().renderMutex);
- if(lock.locked()){
- #else
- boost::try_mutex::scoped_try_lock lock(Omega::instance().renderMutex,boost::defer_lock);
- if(lock.owns_lock()){
- #endif
- this->makeCurrent();
+ //#if BOOST_VERSION<103500
+ // boost::try_mutex::scoped_try_lock lock(Omega::instance().renderMutex);
+ // if(lock.locked()){
+ //#else
+ // boost::try_mutex::scoped_try_lock lock(Omega::instance().renderMutex,boost::defer_lock);
+ // if(lock.owns_lock()){
+ //#endif
+ //this->makeCurrent();
    QGLViewer::paintGL();
- }
- this->doneCurrent();
+ //}
+ //this->doneCurrent();
 }

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

The locking doesn't work for you then at all!

I just installed boost 1.37 (I didn't know it was in repositories for jaunty) and will fix it properly.

The code was written blindly just following the docs as I had 1.34 till now. Sorry.

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

Try r1936 please (and no patches of GLViewer! ;-) )

Revision history for this message
Sergei Dorofeenko (sergei.dorofeenko) wrote :

Thanks! All work!

Changed in yade:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.