OpenFlipper-Free issueshttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues2016-04-08T08:09:34Zhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/38Implement scripting include statement2016-04-08T08:09:34ZJan Möbiusmoebius@cs.rwth-aachen.deImplement scripting include statementin order to streamline and simplify my scripts (often 300-500 lines), I would like to outsource recurring passages into separate scripts and call them from a main script. I can execute scripts using the scripting interface (ScriptInterfa...in order to streamline and simplify my scripts (often 300-500 lines), I would like to outsource recurring passages into separate scripts and call them from a main script. I can execute scripts using the scripting interface (ScriptInterface::executeFileScript()) within my plugin, but can I do so within a script? My questions:
* Is it possible to execute a script within another script.
* If so, how can I pass arguments (such as an object id to be used within the called script) and how can I get a return value (e.g. object id of newly created object).
* If not, any ideas on how to best implement it.OpenFlipper 3.0Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/178Include what you use job for OpenFlipper2021-02-01T12:07:40ZJan Möbiusmoebius@cs.rwth-aachen.deInclude what you use job for OpenFlipperPlease create a new build job which uses include what you use (Linux only):
Maybe we need to include a mapping file to handle Qt 5 correctly
Beispiel:
cmake -DCMAKE_CXX_INCLUDE_WHAT_YOU_USE="iwyu" ../OpenFlipper-FreePlease create a new build job which uses include what you use (Linux only):
Maybe we need to include a mapping file to handle Qt 5 correctly
Beispiel:
cmake -DCMAKE_CXX_INCLUDE_WHAT_YOU_USE="iwyu" ../OpenFlipper-FreeJohannes LenzenJohannes Lenzenhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/176Intermittent UIC related compile failures with CMake 3.18 on Windows2020-11-20T09:13:02ZMartin HeistermannIntermittent UIC related compile failures with CMake 3.18 on WindowsWith the following setup, in many compile runs, some `ui_*.h` files are not found, i.e. UIC is not run:
- Windows 10
- MSVC 2019
- Qt 5.15
- CMake 3.18
Sometimes, regenerating the project, switching between release/debug types ...With the following setup, in many compile runs, some `ui_*.h` files are not found, i.e. UIC is not run:
- Windows 10
- MSVC 2019
- Qt 5.15
- CMake 3.18
Sometimes, regenerating the project, switching between release/debug types and full solution rebuilds actually yield a success, but I haven't been able to figure out any pattern.
Not all `ui_*.h` files are missing (the build results in an incomplete OF that works, but is without the DataControl plugin), however I also couldn't make out what makes the failing ones special. The following ones 'tend' to fail:
- `ui_QtMaterialDialogUi.h`
- `ui_lightWidget.h`
With CMake 3.14 (everything else unchanged), the issues do not seem to appear.
This behavior occurs both on my machine and on the machine of one of our students.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/93Investigae CMAKE performance2017-05-23T13:15:04ZMartin SchultzInvestigae CMAKE performanceCMAKE has become quite slow. investigate possible performance issues by means of profiling and analysis of the cmake code.CMAKE has become quite slow. investigate possible performance issues by means of profiling and analysis of the cmake code.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/173Loading Objects moves progressbar behind filepicker2020-08-13T13:11:32ZZain SelmanLoading Objects moves progressbar behind filepickerAs apparent in the screenshot the filepicker hovers above the progressbar window. Not knowing whether it is loading the file or not, can be confusing if not aware of this and the progressbar is completely covered (as it is default).
![im...As apparent in the screenshot the filepicker hovers above the progressbar window. Not knowing whether it is loading the file or not, can be confusing if not aware of this and the progressbar is completely covered (as it is default).
![image](/uploads/faf24a3d0d42a2e16ac17979aeae9802/image.png)https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/7Loading PolyMeshes to OpenFlipper results in unusable normals with values INF...2015-11-03T20:21:26ZChristopher TenterLoading PolyMeshes to OpenFlipper results in unusable normals with values INF/NANLoad a polymesh with a non-convex polygon (attached) and the halfedge normals as they are stored in OpenMesh are unusable.
Normals are set to value -1.#INF.
This doesn't happen for triangle meshes or poly meshes in which all polygons...Load a polymesh with a non-convex polygon (attached) and the halfedge normals as they are stored in OpenMesh are unusable.
Normals are set to value -1.#INF.
This doesn't happen for triangle meshes or poly meshes in which all polygons are convex.
attached:
starbox.obj: obj file to load containing a star shape polygon.
loaded.obj: the mesh as it is stored in OpenMesh after importing
[loaded.obj](/uploads/82fa24351f3cd237a4ef5ad3289c4ca0/loaded.obj)
[starbox.obj](/uploads/6b00aafba305710db6f165cbfdc8e36d/starbox.obj)
https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/32MemInfo Plugin shows incorrect data on OS X2016-05-11T09:23:39ZAlexander DielenMemInfo Plugin shows incorrect data on OS XThe MemInfo plugin shows incorrect data due to a conversion error.
I have attached a possible fix.
The resulting numbers are somewhat more plausible. However, they are not consistent with Activity Monitor and htop.
[memory.diff]...The MemInfo plugin shows incorrect data due to a conversion error.
I have attached a possible fix.
The resulting numbers are somewhat more plausible. However, they are not consistent with Activity Monitor and htop.
[memory.diff](/uploads/a27b0ed1d9263cdda60ed34b742693c0/memory.diff)
Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/3MemoryInformation on OSX2015-11-09T08:54:54ZMartin SchultzMemoryInformation on OSXI fixed the redmine issue #2533 (btw it would be nice if we only add issues to either redmine or gitlab but using both is confusing)
however i would like to add memory statistics on osx... is there a way to test my code without pushin...I fixed the redmine issue #2533 (btw it would be nice if we only add issues to either redmine or gitlab but using both is confusing)
however i would like to add memory statistics on osx... is there a way to test my code without pushing it to gitlab? Something like local testing on an apple device?https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/89meshConversion fails when converting to polyMesh2017-05-04T12:33:24ZMartin SchultzmeshConversion fails when converting to polyMeshthe scripted code returns always -1 when a mesh is converted to polymesh.
seems to be a type of line 139 where a local copy of the variable newID is used.the scripted code returns always -1 when a mesh is converted to polymesh.
seems to be a type of line 139 where a local copy of the variable newID is used.Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/153MeshInfo on TriMesh without connectivity shows bogus results2018-06-19T08:55:14ZMartin HeistermannMeshInfo on TriMesh without connectivity shows bogus resultsWhen loading point cloud data and using the MeshInfo plugin, it's showing some strange values for face valence (2**32-1), edge length etc (large floats).When loading point cloud data and using the MeshInfo plugin, it's showing some strange values for face valence (2**32-1), edge length etc (large floats).https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/98~MeshObjectSelectionPlugin() crash2017-04-27T10:46:38ZMartin Heistermann~MeshObjectSelectionPlugin() crashThis script crashes on exit (run without -b):
```
core.loadObject("some.obj");
core.exitApplication();
```
I assume the object doesn't matter, attaching just in case.
Backtrace:
```
Trying a backtrace to show what happened last:
Stack ...This script crashes on exit (run without -b):
```
core.loadObject("some.obj");
core.exitApplication();
```
I assume the object doesn't matter, attaching just in case.
Backtrace:
```
Trying a backtrace to show what happened last:
Stack frames: 10
0: OpenFlipper :: backtrace() (+0x26) [0x558fe6cc53f6]
1: OpenFlipper :: segfaultHandling(int) (+0x16a) [0x558fe6cc5e8a]
2: /lib/x86_64-linux-gnu/libc.so.6 :: (+0x33040) [0x7f008d560040]
3: /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 :: QWidget::~QWidget() (+0x47f) [0x7f008f5e9cef]
4: /home/mxn/src/OpenFlipper-Free/build-reldebug/Build/lib/plugins/libPlugin-SelectionMeshObject.so :: MeshObjectSelectionPlugin::~MeshObjectSelectionPlugin() (+0x1fd) [0x7effa051572d]
5: /home/mxn/src/OpenFlipper-Free/build-reldebug/Build/lib/plugins/libPlugin-SelectionMeshObject.so :: MeshObjectSelectionPlugin::~MeshObjectSelectionPlugin() (+0x9) [0x7effa05159f9]
6: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 :: (+0x273839) [0x7f008ecb8839]
7: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 :: (+0x274fcf) [0x7f008ecb9fcf]
8: /lib/x86_64-linux-gnu/libc.so.6 :: __cxa_finalize (+0x8f) [0x7f008d562c8f]
9: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 :: (+0x7ed43) [0x7f008eac3d43]
Backtrace completed, trying to abort now ...
Trying to get additional information (This might fail if the memory is corrupted).
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
[1] 5551 abort (core dumped) OpenFlipper -c crash.ofs
```
Not entirely sure what the problem is - especially as it does not occur when manually exiting OF instead of using core.exitApplication.Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/27Missing Opengl extensions with Qt 5.5.12018-05-08T10:46:13ZMartin SchultzMissing Opengl extensions with Qt 5.5.1I just set up a new arch linux environment and now i am experiencing strange behavior.
Openflipper reports my graphics card does not support the GL_ARB_vertex_buffer_object extension which is wrong since i have an opengl 3.3 context.
...I just set up a new arch linux environment and now i am experiencing strange behavior.
Openflipper reports my graphics card does not support the GL_ARB_vertex_buffer_object extension which is wrong since i have an opengl 3.3 context.
i investigated this since someone else told me about the same behavior a few months ago.
i attached the output of openflpper and made it print all extensions found in QOpenglcontext.extensions()
as it turns out my glxinfo shows the mentioned extension, while qt doesn't.
when i hit the ignore button openflipper starts, but the window is never repainted.[glxinfo_output](/uploads/1e0ddae0475e4f6b990b5dc4981b9969/glxinfo_output)
[openflipper_output](/uploads/5033a54adc2e319d4661101126efc9fb/openflipper_output)
https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/110More detailed documentation of addEmptyObject2017-08-02T09:13:13ZMartin SchultzMore detailed documentation of addEmptyObjectThe documentation explains the very basics of how to add an empty object to openflipper, but it does not mention the signal slot structure, that is involved with it.
Explaining how addEmptyObject is processed in the documentation woul...The documentation explains the very basics of how to add an empty object to openflipper, but it does not mention the signal slot structure, that is involved with it.
Explaining how addEmptyObject is processed in the documentation would help to avoid out of order execution.
Maybe in combination with a short example similar to the one in https://www.graphics.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/issues/108https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/71More efficient PrincipalAxisNode rendering2017-05-04T12:33:26ZHans-Christian EbkeMore efficient PrincipalAxisNode renderingPrincpialAxisNode (ACG/Scenegraph/PrincipalAxisNode.cc) is rendered in a rather inefficient manner: Axis nodes consist of only 3 colors but every vertex has its individual color. That's some major waste of GPU memory. At the point of thi...PrincpialAxisNode (ACG/Scenegraph/PrincipalAxisNode.cc) is rendered in a rather inefficient manner: Axis nodes consist of only 3 colors but every vertex has its individual color. That's some major waste of GPU memory. At the point of this writing, the file in question is not yet merged into master but in branch move_principal_axis_node_from_physim.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/100move away from deprecated QTScript to QJSEngine based scripting2020-11-24T08:33:04ZJascha Wedowskimove away from deprecated QTScript to QJSEngine based scriptingQTScript is deprecated since QT 5.5 (?), recommended alternative is QJSEngine.
Problems with moving away are:
* QTScript systems are present in interfaces -> interfaces will have to change
* As a result of this, plugins using the script...QTScript is deprecated since QT 5.5 (?), recommended alternative is QJSEngine.
Problems with moving away are:
* QTScript systems are present in interfaces -> interfaces will have to change
* As a result of this, plugins using the scripting system have to be touched
First step: Abstract direct usage of QTScript classes in usage code (i.e. PropertyVisPlugin) to find suitable new abstraction
When this is done, make all usage code use new abstraction, then incrementally port internals to QJSEngine.Jascha WedowskiJascha Wedowskihttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/52Mysterious Progress Dialog Pops Up and Occasionally Crashes OpenFlipper2017-05-04T12:33:26ZHans-Christian EbkeMysterious Progress Dialog Pops Up and Occasionally Crashes OpenFlipperOn a vanilla OpenFlipper-Free build, without ~/.OpenFlipper folder (i.e. no stale settings), when you open the File -> Options dialog and wait for 3-5 seconds an unlabeled progress dialog pops up (see screen shot). When you close it by c...On a vanilla OpenFlipper-Free build, without ~/.OpenFlipper folder (i.e. no stale settings), when you open the File -> Options dialog and wait for 3-5 seconds an unlabeled progress dialog pops up (see screen shot). When you close it by clicking the "Cancel" button on roughly 1 out of 3 instances OpenFlipper crashes.
# Crash Log
<pre>
=====================================================
OpenFlipper or one of its plugins caused a Segfault.
This should not happen,... Sorry :-(
=====================================================
Trying a backtrace to show what happened last:
Stack frames: 20
0: ./Build/bin/OpenFlipper(_Z9backtracev+0x1e) [0x45f05e]
1: ./Build/bin/OpenFlipper(_Z16segfaultHandlingi+0x2da) [0x45f4fa]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7f89559710e0]
3: ./Build/bin/OpenFlipper(_ZN13OptionsWidget14cancelDownloadEv+0x65) [0x561bb5]
4: ./Build/bin/OpenFlipper() [0x5a1e85]
5: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x8ee) [0x7f89572e235e]
6: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x36bc75) [0x7f89584e8c75]
7: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x8ee) [0x7f89572e235e]
8: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN15QAbstractButton7clickedEb+0x32) [0x7f895865c282]
9: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x24f195) [0x7f89583cc195]
10: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x24fd29) [0x7f89583ccd29]
11: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN15QAbstractButton17mouseReleaseEventEP11QMouseEvent+0xd4) [0x7f89583ccec4]
12: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x2b8) [0x7f89583131d8]
13: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f89582d24cc]
14: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xb65) [0x7f89582d7e15]
15: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xc3) [0x7f89572b4663]
16: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0x3a2) [0x7f89582d6aa2]
17: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x1b0bdd) [0x7f895832dbdd]
18: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(+0x1b2efb) [0x7f895832fefb]
19: /ACG/acgdev/gcc-4.9-x86_64/qt-5.5.1/5.5/gcc_64/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f89582d24cc]
Backtrace completed, trying to abort now ...
Trying to get additional information (This might fail if the memory is corrupted).
DrawMode Viewer 0 Solid (smooth shaded)
DrawMode Viewer 1 Solid (smooth shaded)
DrawMode Viewer 2 Solid (smooth shaded)
DrawMode Viewer 3 Solid (smooth shaded)
Aborted (core dumped)
</pre>
# Screen Shot
![bug](/uploads/b5fa81fb0889a8187b2f126c72c5ffe9/bug.png)Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/127Objects are rendered on top of the embedded log view2017-09-18T14:17:16ZMartin SchultzObjects are rendered on top of the embedded log view![Screenshot_2017-09-18_13-52-49](/uploads/9162edd4239f41cbd37003d07ee59453/Screenshot_2017-09-18_13-52-49.png)
affects all platforms on all opengl modes (compat and core)
occurs only on core profile branch, current unstable does not ex...![Screenshot_2017-09-18_13-52-49](/uploads/9162edd4239f41cbd37003d07ee59453/Screenshot_2017-09-18_13-52-49.png)
affects all platforms on all opengl modes (compat and core)
occurs only on core profile branch, current unstable does not exhibit this.https://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/33obj loader assertion in debug mode2016-04-08T08:08:45ZMartin Schultzobj loader assertion in debug modein debug mode the obj loader causes an assertion since it tries to add widgets from a background thread, which is not allowed.in debug mode the obj loader causes an assertion since it tries to add widgets from a background thread, which is not allowed.Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/4Obj Loader crashes when loading obj with multiple meshes2015-11-12T13:31:05ZMartin SchultzObj Loader crashes when loading obj with multiple meshesChristoph reported a crash when loading obj files with multiple meshes.
unfortunately the error seems to be caused in a separate thread
![error_screen](/uploads/85a21ed6506fa5adf60c250ed6d3c7c2/error_screen.jpg)
[boxes.obj](/uploads...Christoph reported a crash when loading obj files with multiple meshes.
unfortunately the error seems to be caused in a separate thread
![error_screen](/uploads/85a21ed6506fa5adf60c250ed6d3c7c2/error_screen.jpg)
[boxes.obj](/uploads/5c36e8aa5b8d88afe62c5e1983bd2326/boxes.obj)
Martin SchultzMartin Schultzhttps://gitlab.vci.rwth-aachen.de:9000/OpenFlipper-Free/OpenFlipper-Free/-/issues/161Oldest supported Qt version?2018-12-05T13:31:38ZMartin HeistermannOldest supported Qt version?Hello,
In OpenFlipper-Free/Plugin-PropertyVis!11, I used `QOverload` to disambiguate signals, [which was only introduced in Qt 5.7](http://doc.qt.io/qt-5/qtglobal.html#qOverload).
CI tests Qt versions down to ([now unsupported](https://...Hello,
In OpenFlipper-Free/Plugin-PropertyVis!11, I used `QOverload` to disambiguate signals, [which was only introduced in Qt 5.7](http://doc.qt.io/qt-5/qtglobal.html#qOverload).
CI tests Qt versions down to ([now unsupported](https://en.wikipedia.org/wiki/Qt_version_history#Qt_5)) 5.5.1 and thus fails.
Is this for legacy reasons or do we really need to support old Qt?
In the latter case, I'll of course backport my code, but before doing that, I'd rather ask in case this is just an old artifact.Martin HeistermannMartin Heistermann