Create a Forum Topic by Logging In or Creating an Account

ListBox action procedure debugging

Tue, 01/31/2012 - 07:10 am

Hi all. I have written a ListBox action procedure (new-style structure-based) to select waves to be displayed in a plot window. The procedure uses a switch on lba.eventCode. In attempting to debug (break point set at start of LB action proc) the debugger will only follow through on event code 1 (mouse down) which have set to print "selected" for debugging purposes. I have set the append selected trace and remove previous trace code to happen on event code 4 (cell selected). It clear that both event codes pass through the action procedure as both portions of code execute, however the debugger will only follow through event code 1. When I use an old-style action proc the debugger will follow both event codes. Is there any way I can make this happen for the new-style structure-base proc? I haven notice that event code 4 goes through first (I think) as the functional add/remove traces code works before the debugger pops up for event code 1.

Many thanks,
Tom

johnweeks

Tom-

Do you mean that with the new-style action procedure, you see only one event in each invocation of the action procedure? If that's what you mean, then it is by design- the new-style procedures deliver only one event code per invocation. You should see both events in the lba.eventCode, but the lba.eventCode2 will not be used.

If that is not what you mean, please post an Igor experiment file that shows the problem.

John Weeks
WaveMetrics, Inc.
support@wavemetrics.com

January 31, 2012 at 01:14 pm - Permalink