-
Notifications
You must be signed in to change notification settings - Fork 24
Dikjstra's shortest path ? #39
Comments
A quick follow up to this comment: is there an efficient alternative to know if a pair of nodes are connected in a graph? |
For reference, here are the details:
:param One usage would be: |
QOpenGL module is marked as deprecated since a while now so it is time to remove its use from the Talipot codebase and promote the use of QOpenGL* classes directly integrated in the QtGui module. The big difference between QOpenGL and QtOpenGL from Qt5 is that all rendering is performed in framebuffer objects, there is no more direct rendering in the underlying os windows with its own OpenGL context. Talipot OpenGL rendering also follows that idiom, all renderings are performed offscreen using a shared OpenGL context. This also means that there is no more QGLWidget as viewport for QGraphicsView. Talipot OpenGL scene are now converted to QImage in order to display them using the default Qt raster rendering engine. This should fixes the numerous rendering glitches observed on MacOS. First thing observed after the migration is a consequent performance boost in OpenGL rendering when using an Intel GPU on a Linux host machine (especially when selecting elements, it is now 10 times faster on debian stable).
Hi everyone,
I'm posting this to keep it as a reminder (it should be easy to adapt from the existing code).
Although Dikjstra is implemented in the path highlighter interaction plugin (https://github.com/Tulip-Dev/tulip/tree/master/plugins/interactor/PathFinder/PathFinding/Dikjstra), path finding between two nodes is one most-useful basic graph manipulation lacking in Tulip core.
DFS and BFS are now directly ported to the python api, so maybe the PathFinding component could become a similar component? (path finding itself does not depend on GUI elements).
Cheers,
The text was updated successfully, but these errors were encountered: