This application is just working very well and is very useful.
I am for the moment working on version 2011a and will soon update to 2013. Do you know if any update will be done in order to be compatible with this version ? (To avoid to loose my work...)
Anyway, great job !
Have you read "readme.txt" file in "patch" folder, where p-file you've mentioned is located?
It mostly explains why they are there.
It looks like these files are fixed versions of core matlab functions, so developers won't release source code for them. Just hope that those issues would be removed some time.
It's easy to use, however, I've been facing same problem while trying to compile this GUI into standalone application.
When attempting to compile some of your code, warnings are given relative to the P-files missing their associated M-Files.
Here is one example :
Warning: Requirements cannot analyze P-code unless the user provides a corresponding M-code along with the P-code in the
same folder. The dependencies of D:\Codes\MATLAB\GUILayout-v1p14\Patch\getpixelposition.p may not be included in the
completion because its corresponding M-code cannot be found by REQUIREMENTS.
I was wondering if there's any workaround, or if you can release the m-code. Since the main reason to write a gui is to distribute it through standalone projects. Thanks for helping in advance.
There is a small "bug" that makes this package incompatible with the Matlab "Application compiler" app for redistributing compiled stand alone applications.
A work around is the following:
The problem lies with the image locations being hard-linked to the location of the package from the use of "fileparts". I replaced these lines with a test for "isdeployed", for example lines 424/5 of uiextras.TabPanel (iLoadIcon function) to:
this_dir = fileparts( mfilename( 'fullpath' ) );
icon_dir = fullfile( this_dir, 'Resources' );
this_dir = '.';
icon_dir = '.';
I then simply include the resource files in the list of additional files in the app.