M!Table side effects for SalTblDefineDropDownListColumn( ) and SalTblSetFocusCell( )

[James McCall]

 Posted by:  James McCall 

I'll start this post by thanking Michael Stoll for sharing the well thought
through, brilliantly implement and nicely documented M!Table.

I have found a couple of non-critical side effects of M!Table when using
SalTblDefineDropDownListColumn( ) and SalTblSetFocusCell( ). Rather than a
verbose explanation here I'll just reply to this post with a sample
attached.

James McCall

[James McCall]

 Posted by:  James McCall 

Here's the sample, in CTD2000 saved as text

[James McCall]

 Posted by:  James McCall 

Sorry, just noticed that I posted the wrong version of my sample, so please
ignore the previous source code.

The version attached here includes mtbl.apl rather than having the merged
into the source.
It also has the work-around of the row selection problem (basically just
force a re-paint).

[micsto]

 Posted by:  Michael Stoll \(MICSTO\) 

Hi James,

the problems are reproducable and will be fixed in the next version.
The problem is that SAM_Click is sent "in the middle" of the M!Table
processing.

Workaround for the current version:
Use MTM_AreaLBtnDown instead of SAM_Click ( don't forget to activate the
extended messages with MTblEnableExtMsgs ).

Michael