Jump to content
Sign in to follow this  

Bug? Custom Category does not create Custom Top Level Controls Palette

Recommended Posts

VIPM 2011.0.0 (build 1669)


I came across this when developing for Team LAVA, but you can see it in OpenG.


Steps to reproduce the bug (if it can be reproduced)

Create a package with a Custom Category.

Add a functions and a controls palette.


Expected behavior (what would happen if the bug didn't exist)

The package creates Custom Top Level Menus for both the Functions and Controls Palettes.


Actual, observed behavior (the bug)

No Custom Top Level Control Menu is created.

Therefore the default is used.


Using OpenG as an example which makes use of the Custom Category function you will see that the Functions Palette is fine:



However, the Controls Palette is not:



The Buttons package (only package that has controls) is installed and the VIPB specifies a Custom Category:



You can see the dir.mnu file (which is what the Categories folder calls its top level menu) is missing.



Which is also evident in the spec file:



A Top Level Palette is still created as the folder "OpenG" exists (no leading underscore) but the name (folder name) and icon use default data.


I have a workaround for now which is to make my own palette .ogp package (just like in the old days) and link to that.




Edited by jgcode

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.