#6043 closed defect (fixed)
Library Browser missing View Documentation menu option
Reported by: | Owned by: | Adeel Asghar | |
---|---|---|---|
Priority: | blocker | Milestone: | 1.16.0 |
Component: | OMEdit | Version: | v1.16.0-dev |
Keywords: | View Documentation | Cc: |
Description
The https://openmodelica.org/doc/OpenModelicaUsersGuide/1.14/omedit.html version 1.14 OpenModelica User Guide "Libraries Browser" description has an image that shows the "View Documentation" menu item for the ChuaCircuit class.
When I right click on the ChuaCircuit class for version 1.14.1-64bit, I see "Information" instead of "View Documentation". As shown in the image below, clicking on "Information" brings up a window with version information fields but without any values. This does not look right. I suspect that the "View Documentation" menu option is inadvertently missing and that the "Information" menu item pop-up should include the appropriate version number values. It would be helpful if the "View Documentation" menu option was available and showed the appropriate class documentation when selected. I suspect that this is how the software is supposed to work.
Change History (5)
comment:1 by , 4 years ago
Component: | Documentation → OMEdit |
---|---|
Milestone: | Future → 1.16.0 |
Owner: | changed from | to
Priority: | high → blocker |
Status: | new → assigned |
Version: | v1.14.1 → v1.16.0-dev |
comment:3 by , 4 years ago
The view documentation menu item was removed some time ago but the documentation is not updated. I will update it.
comment:4 by , 4 years ago
Thank you for fixing the documentation. It would be nice if that feature comes back in a future version.
comment:5 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
The documentations is fixed in 85cad8f/OpenModelica.
Context menu item is not available but there are other ways to open Documentation Browser. Click on the documentation view button in ModelWidget or use the View menu.
You are absolutely right, there is both a problem with OMEdit and with the documentation. The problem is still there with 1.16.0-dev.03. I guess we should fix it for the 1.16.0 release.
@adeas31, what do you think?