Path: news.mathworks.com!not-for-mail
From: "helper " <spamless@nospam.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Listbox mousedown problems
Date: Tue, 13 May 2008 00:04:04 +0000 (UTC)
Organization: Timothy S. Farajian, Inc.
Lines: 15
Message-ID: <g0altk$221$1@fred.mathworks.com>
References: <g09d97$ir0$1@fred.mathworks.com> <g09toa$j63$1@canopus.cc.umanitoba.ca>
Reply-To: "helper " <spamless@nospam.com>
NNTP-Posting-Host: webapp-05-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1210637044 2113 172.30.248.35 (13 May 2008 00:04:04 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Tue, 13 May 2008 00:04:04 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 1272923
Xref: news.mathworks.com comp.soft-sys.matlab:468037


> Did you try recording the Value parameter of the listbox 
before
> the change and then setting the Value of the listbox after
> the String has changed? The Value parameter controls 
which line
> of the listbox is the current line.

That will not work for me.

The problem is that although the mousedown event changes 
which element appears to be selected on the listbox, and 
causes the editbox callback to fire, it does not change 
the "Value" property in MATLAB.  The "Value" property does 
not change until the mouseup event.