Assignin variables in a stand-alone application
2 ビュー (過去 30 日間)
古いコメントを表示
I have a GUI with a button that uses the assignin() function to send variables to the 'base' for debug and analysis purposes when running the code in Matlab. What happens to these variables when the application is run as a stand-alone version? Should I disable the button when compiled as a stand-alone? Is there a test I can perform to determine if the button should be disabled or enabled?
3 件のコメント
Walter Roberson
2012 年 6 月 4 日
GUI functionality _is_ supported with MATLAB Compiler. GUI functionality is not, however, supported with MATLAB Coder.
採用された回答
Walter Roberson
2012 年 6 月 4 日
The variables still get assigned to the base workspace. The base workspace would get destroyed (along with all other workspaces) when the standalone application exited, but the variables can be used until that point.
If it does not make sense in your context to be able to save those variables in stand-alone mode, use isdeployed()
4 件のコメント
Walter Roberson
2012 年 6 月 6 日
"global variables" would be one way of looking at it, but the base workspace is distinct from the workspace of global variables.
その他の回答 (1 件)
Walter Roberson
2012 年 6 月 22 日
My previous answer might have been wrong about the base workspace existing in compiled applications. I am having difficulty finding documentation on this matter, but it is implied by Loren in http://blogs.mathworks.com/loren/2010/11/18/deploying-standalone-applications/ and in a small number of ambiguous cssm postings .
(Some day I'm going to be able to afford to get a MATLAB Compiler license and try these things myself... But it probably won't be soon.)
0 件のコメント
参考
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!