Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: UITable DataChangedCallback-update within callback
Date: Thu, 12 Jan 2012 11:18:07 +0000 (UTC)
Organization: Continental Teves AG &#38; Co. OHG
Lines: 11
Message-ID: <jemfhf$bdo$1@newscl01ah.mathworks.com>
References: <jekbvl$dab$1@newscl01ah.mathworks.com> <jekurb$khf$1@newscl01ah.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: www-04-blr.mathworks.com
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: newscl01ah.mathworks.com 1326367087 11704 172.30.248.35 (12 Jan 2012 11:18:07 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Thu, 12 Jan 2012 11:18:07 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 2885627
Xref: news.mathworks.com comp.soft-sys.matlab:754522

"Yair Altman" wrote in message <jekurb$khf$1@newscl01ah.mathworks.com>...

> Turning off a callback within that same callback is generally ignored although no error is generated. Instead, use a programmatic bail-out mechanism. For example: http://UndocumentedMatlab.com/blog/controlling-callback-re-entrancy/

Hello Yair,

thanks (again) for the right hint.

I finally decided not to use the isMultipleCall but attach some Userdata to the underlying figure. This, basically following the same route, resolves my issue.

Alexander