v1.25.9

-- Fix but found in StimEditGUI. When changing current element from one run to another, an unsaved change made to the stims of the previous run remains in effect even though the user clicked NO to Save question before the current element is changed.

-- Added function errorCheck() in extractButtondownPoints() to check the coherence of a user button down selection in StimEditGUI axes (or any other GUI). There seems to be a bug in Matlab R2020a where you select an axes region, rbbox correctly reports that a rectangle was selected - in other words, the 3rd number in finalRect is > 0 - BUT p2 is equal to p1 (meaning only a point has been selected), contradicting what rbbox shows. This problem does not exist in say R2017b. So to compensate for this bug we check finalRect against {p1,p2} and if finalRect is showing a size > 0 then we add the comparable size to p2.