fvpolpeta / devide

Automatically exported from code.google.com/p/devide
BSD 3-Clause "New" or "Revised" License
2 stars 1 forks source link

GUI should refer to modules by name if possible #103

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Various parts of the UI refer to modules by their type. The most important 
examples are the module configuration views and progress messages. This can 
cause confusion when multiple modules of the same type are used in a network. 
Worse, in some cases, the module shown in a progress message is an internal 
module of the actual module on the canvas. 

To solve this, add the name of a module (if set by the user):
* Progress messages: rather than ``vtkImageContinuousDilate3D: Performing 
greyscale 3D dilation'' use ``vtkImageContinuousDilate3D "Narf": Performing 
greyscale 3D dilation''. If the message refers to an internal module, prepend 
the on-canvas module: ``closing "Narf": vtkImageContinuousDilate3D: Performing 
greyscale 3D dilation''.
* Configuration views and other windows related to modules: prepend the name 
of the module to the title bar. Instead of ``slice3dVWR 3D view'' use ``Poit 
(slice3dVWR) 3D view''. Prepending names to window titles helps to locate 
specific windows in an over-crowded taskbar.

Original issue reported on code.google.com by stef.bus...@gmail.com on 18 Sep 2008 at 3:11