| |
| META TOPICPARENT |
name="DpHipe" |
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END --> |
| |
As part of giving better support to developers and to help diagnose GUI problems, a Debug preferences category has been added to HIPE. |
|
<
< | The preference Enable debug in that new category shall be switched on to let debug services be run individually. When this preference is set, debug services will also be controllable through the Tools > Debug menu, which will be invisible while that master preference is unset. Current options for debug: |
>
> | The preference Enable debug in that new category shall be switched on to let debug services be run individually. When this preference is set, debug services will also be controllable through the Tools -> Debug menu, which will be invisible while that master preference is unset. Current options for debug: |
| | |
|
<
< |
- Check the painting of graphical components: it checks that all painting is done in the EDT. If it is not the case then you have to move code to the EDT.
- Check that the application is responsive: checks that no event in the EDT takes more than a second to process and that threads are not (inter)blocked. If it is the first case then you need to move code out of the EDT. If it is the second case then you need to redesign shared resource access.
- Paint special border on the pointed component: this helps to diagnose GUI layout problems.
|
>
> |
- Check the painting of graphical components: it checks that all painting is done in the EDT. If it is not the case then you have to move code to the EDT.
- Check that the application is responsive: checks that no event in the EDT takes more than a second to process and that threads are not (inter)blocked. If it is the first case then you need to move code out of the EDT. If it is the second case then you need to redesign shared resource access.
- Paint special border on the component pointed at: this helps to diagnose GUI layout problems.
|
| |
Provide an image preview of a FITS file |
| |
If you want to store data at application exit like these, for being recovered at next HIPE start up, you can do it yourself by writing files within a site area (see previous tip). |
|
<
< | However, using the session persistor framework instead may save you some coding. Moreover, your session items would be exported and imported automatically with the File > Session > Export / Import options for free. |
>
> | However, using the session persistor framework instead may save you some coding. Moreover, your session items would be exported and imported automatically with the File -> Session -> Export / Import options for free. |
| |
The following example shows how to use it: |
| |
| Navigator |
ia_gui_apps |
herschel.ia.gui.apps.views.navigator.NavigatorView |
Outline
|
ia_gui_apps
|
herschel.ia.gui.apps.views.outline.OutlineView
herschel.ia.gui.apps.views.outline.OutlineComponent
herschel.ia.gui.apps.components.outline.* |
Script editor
|
ia_jconsole
|
herschel.ia.jconsole.views.JythonEditorComponent
herschel.ia.jconsole.views.TextEditorComponent |
|
|
<
< |
Console
|
ia_jconsole
|
herschel.ia.jconsole.views.ConsoleView
herschel.ia.jconsole.jython.Interpreter
herschel.ia.jconsole.jython.CommandExecutor |
Variables view
|
ia_gui_apps
|
herschel.ia.gui.apps.views.variables.VariablesView
herschel.ia.gui.apps.views.variables..NameSpaceTree |
|
>
> |
Console
|
ia_jconsole
|
herschel.ia.jconsole.views.ConsoleView
herschel.ia.jconsole.jython.Interpreter
herschel.ia.gui.kernel.command.CommandExecutor |
Variables view
|
ia_gui_apps
|
herschel.ia.gui.apps.views.variables.VariablesView
herschel.ia.gui.apps.views.variables.NameSpaceTree |
|
| |
Tasks view
|
ia_task
|
herschel.ia.task.views.TasksView
herschel.ia.task.views.TaskTree |
|
