How to disable RTW builds invoked by non-script means
3 views (last 30 days)
Show older comments
I'm after preventing users from executing a code build via the built-in mechanisms (Ctrl-B shortcut, Build buttons in dialogs, etc), and forcing them to use a build script (which itself will call slbuild() or similar).
I can use the sl_customization() to disable individual commands, buttons, etc, but that is a bit hit and miss (e.g. select then deselect "Code generation only" and build button re-enables) and I can use either a STF or installation specific hook, but that isn't aware of how the build was invoked so I've only been able to look for telltales in the dbstack trace, which doesn't seem robust enough.
Can anyone suggest any other tricks I could use in a hook file, or any other means I could use to achieve this?
Thanks in advance, Graham
0 Comments
Accepted Answer
Ryan G
on 25 Jul 2012
You may be able to disable CTRL-B utilizing:
File -> Preferences -> Keyboard -> Shortcuts and un-assinging the CTRL+B command.
In terms of the buttons I think the sl_customization is the best option. I believe that Simulink will run ALL of the sl_customization files on the path when it opens, not just the first one like the setup.m file.
I do wonder why you have to try so hard to stop users from building code.
0 Comments
More Answers (1)
See Also
Categories
Find more on Startup and Shutdown in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!