Can happen quite often if users don't know that they have to click on the plugin first before they see the plugin documentation.
Revisions and Commits
|Restricted Differential Revision||rMITKe9db8e89bd6e F1 help and doxygen documentation for the standard display.|
|Restricted Differential Revision||rMITKde5a79b64224 Minor text correction.|
|Restricted Differential Revision||rMITK63bf3534beb7 Update Workbench documentation.|
|Restricted Differential Revision||rMITK4dadcf948cc3 Update pictures to current layout.|
|Restricted Differential Revision||rMITK759bf7756993 Text corrections.|
|Restricted Differential Revision||rMITKa69ea181d1c1 Text correction in Workbench and standard display documentation.|
|Restricted Differential Revision||rMITK12b91ad30c8a Reverse renaming steps, remove "editor" in the end.|
|Restricted Differential Revision||rMITK785b889ffbcd F1 help and doxygen documentation for the standard display.|
I am not sure what is exactly done here to reproduce. To get any help page I have to click on a plugin anyway. How would I provoke a blank page?
When I use F1 while the Standard Display is activated I get a blank page for the Standard Display. If that's what is meant than we need to reconsider how to display this specific help page: There is a description of the "four window view" inside src\Plugins\org.mitk.gui.qt.ext\documentation\UserManual\MITKUserManual.dox but we can not move it to the stdmultiwidgeteditor-plugin as it contains more information about the workbench, not only about the standard display.
There are other plugins / widgets that do not provide a help page, e.g. the help plugins :D
We should discuss how we want to handle non-existent help pages.
Please someone have a look at this task and try to understand / reproduce what is happening here.