dan b

I'm working with the min-devkit, and when I change the list of arguments

argument<int> sync_inputs_arg{ this, "sync_inputs", "0 (default) object has sync input, 0: object has no sync input" };

Then the argument list does not seem to update in the context menus in MAX/MSP. Everything else works fine, the object uses the new argument order - the only issue is with the reporting in the max/msp context menus.

e.g. when I build, then open max, and create an instance of my object. When I finish typing the object name, the helper dialogue showing arguments appears: this still shows the argument list as it was before the new build.

I'm working with the min-devkit, and when I change the list of arguments
e.g. by adding 

argument<int> sync_inputs_arg{ this, "sync_inputs", "0 (default) object has sync input, 0: object has no sync input" };

Then the argument list does not seem to update in the context menus in MAX/MSP. Everything else works fine, the object uses the new argument order - the only issue is with the reporting in the max/msp context menus.

e.g. when I build, then open max, and create an instance of my object. When I finish typing the object name, the helper dialogue showing arguments appears: this still shows the argument list as it was before the new build. 

I'm working with the min-devkit, and when I change the list of arguments
e.g. by adding 

argument<int> sync_inputs_arg{ this, "sync_inputs"

argument-list-not-updating-on-rebuild-in-max-7

I'm still not seeing these arguments appear in the context menus. I get no errors, and nothing else has changed, and all other code updates are present in the built external.

Any thoughts on this?
 I'm still not seeing these  arguments appear in the context menus. I get no errors, and nothing else has changed, and all other code updates are present in the built external.

Max's auto-completion is based on slurping info into the database from XML ref-pages for objects.

The good news, since you are using the Min API, is that the ref-pages are generated automatically for you (in the traditional Max you have to create them manually, which most people don't do).

The ref-page won't be generated, however, until after you create an instance of your object. So what you may be seeing is this:

So, knowing this you can create a new version of your object. Then after a moment quit Max and start it again. Then check that your strings are updated.

If all else fails, then you can reset your database (or find it in the file system and delete it) and restart Max. Note that it may take a few minutes to re-build it completely.

Max launches, parses the XML files in the search path and puts the strings in the database.

You try to create your object, but it hasn't actually be created yet, so the info in the database is old.

You get frustrated and kill Max before your new version of your object gets created (so the ref isn't updated) or you kill Max before it updates the database and then it doesn't get the update (or something in that vector of possibilities).

In my case the XML docs are no longer generating on either of my win machines, though they generate from the same package on macOS. I've tried to track this down - but can't see any reason why doc_update() wouldn't be called, and I don't see any errors. I'll raise as an issue on git

Thanks Tim,
In my case the XML docs are no longer generating on either of my win machines, though they generate from the same package on macOS.  I've tried to track this down - but can't see any reason why doc_update() wouldn't be called, and I don't see any errors. I'll raise as an issue on git

For anyone following this thread (now or in the future), the Github conversation is at 

https://github.com/Cycling74/min-devkit/issues/116

For anyone following this thread (now or in the future), the Github conversation is at https://github.com/Cycling74/min-devkit/issues/116 

Argument List not updating on rebuild in MAX 7