From: exosceleton on 22 Jul 2010 09:45 On one figure when i use the "ginput" command Matlab does not fill in the figure displayed underneath the cross-hairs when i move them. What i mean is that when i move my cursor the black cross-hairs move with my cursor, but it leaves behind a white "shadow" where the cross-hairs used to be. So when i move my cursor around i am effectively "painting" my figure white with hundreds of cross hair ghosts, obstructing the view of the object i want to click on. I've tried reproducing the error but right now it is only happening on one .m/.fig set. It's a complicated script though, i do not want to rebuild it from scratch. anyone have any ideas? I cant find any mention of these symptoms anywhere.
From: us on 22 Jul 2010 10:19 "exosceleton" <exosceleton(a)hotmail.com> wrote in message <i29i1b$kg2$1(a)fred.mathworks.com>... > On one figure when i use the "ginput" command Matlab does not fill in the figure displayed underneath the cross-hairs when i move them. > > What i mean is that when i move my cursor the black cross-hairs move with my cursor, but it leaves behind a white "shadow" where the cross-hairs used to be. > So when i move my cursor around i am effectively "painting" my figure white with hundreds of cross hair ghosts, obstructing the view of the object i want to click on. > > I've tried reproducing the error but right now it is only happening on one .m/.fig set. > It's a complicated script though, i do not want to rebuild it from scratch. > > anyone have any ideas? > I cant find any mention of these symptoms anywhere. it - most certainly - is a gpu/gpu-memory/gpu-driver issue... update said driver... us
From: Walter Roberson on 22 Jul 2010 11:29 us wrote: > "exosceleton" <exosceleton(a)hotmail.com> wrote in message > <i29i1b$kg2$1(a)fred.mathworks.com>... >> On one figure when i use the "ginput" command Matlab does not fill in >> the figure displayed underneath the cross-hairs when i move them. >> What i mean is that when i move my cursor the black cross-hairs move >> with my cursor, but it leaves behind a white "shadow" where the >> cross-hairs used to be. >> So when i move my cursor around i am effectively "painting" my figure >> white with hundreds of cross hair ghosts, obstructing the view of the >> object i want to click on. >> >> I've tried reproducing the error but right now it is only happening on >> one .m/.fig set. >> It's a complicated script though, i do not want to rebuild it from >> scratch. >> >> anyone have any ideas? >> I cant find any mention of these symptoms anywhere. > > it - most certainly - is a gpu/gpu-memory/gpu-driver issue... > update said driver... Alternately, the code might have set the EraseMode to something non-default.
From: exosceleton on 23 Jul 2010 03:40 found one that works. apparently version 8.15.10.1749 from May 2009 is better then the ..10.1840 or ..10.2141 version. Now let's hope it does not update itself somehow.
|
Pages: 1 Prev: polyval help: finding the root Next: polyval help: finding the root |