Commits on Source (8)
-
Nick Laurenson authored
fix #29
-
MelanieCarriere authored
During loadLidarState function, the property was applied only if a proxy of the same name of the one saved was found in the pipeline. For exemple : If you save the LidarState with a LidarPacketInterpreter i1 and you open a file using a LidarPacketInterpreter i2 The properties saved from i1 couldn't be applied to i2. This commit allows applying the property to a proxy of the same group. If the property is not found in this proxy, the message is still display to the user.
-
MelanieCarriere authored
[fix] Allow applying a property to a proxy of the same group in LoadLidarState See merge request !149
-
Nicolas Cadart authored
Animation PlayMode and Duration were reset each time Play/Pause buttons were clicked. This prevented using general paraview animations by manually chosing animation settings. Now, the animation PlayMode and Duration is directly updated when the user selects a different playing speed, and Play/Pause buttons have trivial behavior of invoking Play/Pause commands. The animation Duration is also updated when timesteps range changes, e.g. when a new pcap is loaded. NOTE : When upgrading LVCore in your specific LidarView based application, you should consider removing the line `app.scene.UpdateAnimationUsingDataTimeSteps()` in function `applogic.openPCAP()`. Without this change, the speed mode will be set to 'All Frames' when a new pcap will be loaded. By removing this line, the speed mode and animation settings won't be changed, and will be kept as user set them before.
-
Nicolas Cadart authored
Changing speed factor using combo box may lead to animation play mode change. However, if user changes manually the animation play mode, it may be contradictory with the information displayed by the combo box. lqPlayerControlsToolbar now listens to animation play mode changes, and adapt the combo box display accordingly. Furthermore, when a new animations scene is set, lqPlayerControlsToolbar set its PlayMode accordingly with UI speed combo box.
-
Nicolas Cadart authored
Going previous/next frame changes animation mode to 'Snap To Timesteps'. This will set the speed factor text to 'All frames'. Currently, user has to set back themselves the desired speed factor using the combo box. This commit restores previous animation play mode after having snaped to previous/next frame, so that user does not have to set it themselves again using the speed factor combo box. Also, if we are in 'Real Time' play mode with for example a speed factor 'x5', and if we click Next frame, the speed factor will blink to 'All frames' before going back to 'x5'. As this blink is noisy, we block all animations signals to keep it unchanged during operation.
-
Nicolas Cadart authored
Using custom animation play mode in LidarView See merge request !148
-
Nick Laurenson authored
[doc] Add contribution.md and .gitmessage template Closes #29 See merge request !132
Showing
- ApplicationComponents/SaveAndLoadLidarState/lqLoadLidarStateReaction.cxx 8 additions, 0 deletions...onents/SaveAndLoadLidarState/lqLoadLidarStateReaction.cxx
- ApplicationComponents/lqHelper.cxx 35 additions, 0 deletionsApplicationComponents/lqHelper.cxx
- ApplicationComponents/lqHelper.h 8 additions, 0 deletionsApplicationComponents/lqHelper.h
- ApplicationComponents/lqPlayerControlsController.cxx 43 additions, 13 deletionsApplicationComponents/lqPlayerControlsController.cxx
- ApplicationComponents/lqPlayerControlsToolbar.cxx 41 additions, 2 deletionsApplicationComponents/lqPlayerControlsToolbar.cxx
- ApplicationComponents/lqPlayerControlsToolbar.h 1 addition, 0 deletionsApplicationComponents/lqPlayerControlsToolbar.h
- CONTRIBUTION.md 16 additions, 0 deletionsCONTRIBUTION.md
- Documentation/.gitmessage 49 additions, 0 deletionsDocumentation/.gitmessage
CONTRIBUTION.md
0 → 100644
Documentation/.gitmessage
0 → 100644