GETMONDIM (for releases 2014a or less) returns the dimensions of the specified monitor as a 4 element vector [xstart,ystart,width,height] where values are in pixels in the same manner that the 'ScreenSize' property provides. (xstart,ystart) are the absolute coordinates of the lower left corner. The "monitornumber" is a number associated with each monitor (Default=1). Monitor numbering is defined as the row number of the corresponding monitor in the root property 'MonitorPositions'.
The primary monitor is always numbered 1 and always starts at (1,1). 'MonitorPositions' returns coordinates corresponding to the upper left corner and the bottom right corner (Windows convention). Matlab 'Help' on this property is incorrect. GETMONDIM converts these coordinates to the Matlab convention where the lower left corner starts at (1,1). There is a feature with the root property 'ScreenSize'. If the primary monitor's resolution is adjusted after Matlab has started, then the size parameters of 'ScreenSize' are not adjusted while the origin is adjusted. GETMONDIM fixes this by using the 'ScreenSize' origin to correct for the discrepancy. Note that on restarting Matlab the 'ScreenSize' property changes to the correct values!
Update! MATLAB 2014b version and higher fixed some of the bugs with monitor positions. So this utility will probably only work for releases below that version. MATLAB recommends that if the display configuration changes, resolution or monitor positioning, to restart MATLAB. The little bit I played with Java within MATLAB seems to support that as the Java calls return different results before and restarting MATLAB after a configuration change while MATLAB's MonitorPositions property remains unchanged.Therefore I recommend restarting MATLAB and using the MonitorPositions property to get screensize information.
Mirko Hrovat (2020). Get Monitor Dimensions (https://www.mathworks.com/matlabcentral/fileexchange/19054-get-monitor-dimensions), MATLAB Central File Exchange. Retrieved .
The bugs have been apparently fixed in release 2014b and above. Therefore this utility should still work for releases 2014a and below. Description has been updated.