|
osdir.com mailing list archive |
|
Subject: imshow doesn't accept the same arguments as the one in matlab - msg#00037List: gnu.octave.bugsThe Octave implementation of imshow, doesn't accept the same arguments as the corresponding function in Matlab. I'm personaly missing the ability to set the display range. I tried to change the Octave implementation, but found it to be more easy to develop a new version. So I'm attaching an implementation of imshow that behaves like the one in matlab (except it doesn't handle the 'XData' and 'YData' parameters). SÃren
Bug-octave mailing list Bug-octave@xxxxxxxxxx https://www.cae.wisc.edu/mailman/listinfo/bug-octave Thread at a glance:
Previous Message by Date: click to view message previewRemove global variable from colormapHi, The attached patch removes the global variable __current_color_map__ from the colormap function and replaces it with a persistent (static) variable. That way the user is forced to use the colormap function to change the colormap, and there is one less __* variable (less polution). SÃren 2006-08-12 SÃren Hauberg <hauberg@xxxxxxxxx> * colormap.m: Change global variable to persistent. colormap.patch Description: Text Data _______________________________________________ Bug-octave mailing list Bug-octave@xxxxxxxxxx https://www.cae.wisc.edu/mailman/listinfo/bug-octave Next Message by Date: click to view message previewrgb2ind doesn't accept ND arraysHi, The current implementation of colormap accepts an rgb image given in three matrices. The attached patch makes colormap also accept an rgb image given as a 3D array. SÃren 2006-08-12 SÃren Hauberg <hauberg@xxxxxxxxx> * rgb2ind.m: Make rgb2ind accept ND arrays. rgb2ind.patch Description: Text Data _______________________________________________ Bug-octave mailing list Bug-octave@xxxxxxxxxx https://www.cae.wisc.edu/mailman/listinfo/bug-octave Previous Message by Thread: click to view message previewRemove global variable from colormapHi, The attached patch removes the global variable __current_color_map__ from the colormap function and replaces it with a persistent (static) variable. That way the user is forced to use the colormap function to change the colormap, and there is one less __* variable (less polution). SÃren 2006-08-12 SÃren Hauberg <hauberg@xxxxxxxxx> * colormap.m: Change global variable to persistent. colormap.patch Description: Text Data _______________________________________________ Bug-octave mailing list Bug-octave@xxxxxxxxxx https://www.cae.wisc.edu/mailman/listinfo/bug-octave Next Message by Thread: click to view message previewimshow doesn't accept the same arguments as the one in matlabOn 12-Aug-2006, Søren Hauberg wrote: | The Octave implementation of imshow, doesn't accept the same arguments | as the corresponding function in Matlab. I'm personaly missing the | ability to set the display range. | I tried to change the Octave implementation, but found it to be more | easy to develop a new version. So I'm attaching an implementation of | imshow that behaves like the one in matlab (except it doesn't handle the | 'XData' and 'YData' parameters). The original version had a few tests and some demos. Can you please preserve those? Also, is the new version backward compatible with the old? If not, why not? For Octave, please don't use StudlyCaps for variable names. To match other error messages, don't capitalize them or end them with a period. Instead of warning(["imshow: Input argument number " num2str(narg) " is unsupported."]) please use warning ("imshow: input argument number %d is unsupported", narg); Thanks, jwe Loading Comments...
|
|
