fourMs / VideoAnalysis

A standalone application for creating visualizations and extract motion features from video files.
https://www.uio.no/ritmo/english/research/labs/fourms/downloads/software/VideoAnalysis/
8 stars 2 forks source link

Add documentation to help #16

Closed alexarje closed 4 years ago

alexarje commented 4 years ago

I found the documentation under About, but it is possible to also get it as an entry under Help in the menu?

balintlaczko commented 4 years ago

Yes, that was the way I envisioned it originally, but then while working with the [menubar] object, it became clear that it only allows an about section, and you cannot put anything in the help - at least I haven't found an obvious way yet. That is way it ended up as a half-easter-egg in the About section (since in Windows, About is also under Help). I will try it again now! In worst case we can always just make another menu item for it.

balintlaczko commented 4 years ago

Indeed can re-confirm, that it is not allowed to put anything in the Help menu. However, this should not stop us doing it anyway. After some research and digging, I could manage to remove all the useless things from the menu + adding my new Help menu item by editing the ./resources/interfaces/maxinterface.json . Here is how it looks like now: image

In File: image

...and in Help: image

There is my new clickable Help entry. I have to test this though, it is hard to see at this point if the clicking can be listened to. If the listening works though, this means we finally have a full control over how our menu looks like. The changes seemingly kept already existing functionality and behavior intact.

balintlaczko commented 4 years ago

After some more tweaking of the maxinterface.json I have this layout now: image In File: image In Help: image I will start to test now if we can listen to click events from these new custom entries.

balintlaczko commented 4 years ago

Another status report after a bit more "brain surgery" of Max: though it is possible to create custom menu items by manually modifying the maxinterface.json there is a problem with this approach, namely that the interpreter/compiler of the [menubar] script still won't let you use them, and I found no way to bypass this. What is simpler, and maybe even more consistent is to purge the "normal" File and Help menus all together from maxinterface.json, and create aliases in the [menubar] script. This way I got the same-looking result as in the previous comment (without the keyboard shortcuts) but with being able to listen to my File and Help menu items the same way as any other menu items in the [menubar]. Bottom line is that through some mild hacking we will be able to:

I will start to implement the necessary changes in the root patch and [VA_menubar], and get back here with the results.

balintlaczko commented 4 years ago

Done! NB. if your maxinterface.json is the default one you won't be able to see this change in the patch, only in the build (and only if you follow the instructions in _build_info/buildchecklist.txt). Alternatively, you can do what I did on my system: swapping the maxinterface.json found at (on Windows) C:\Program Files\Cycling'74\Max 8\resources\interfaces\maxinterface.json. But back up the original one, just in case. That way it will work in the patch too. Here is how it looks in the build: image Upon clicking on this, the embedded doc browser opens. Since we moved it from the About window, that one looks like this now: image

alexarje commented 4 years ago

Great, well done!