My perception of the dropdown in the edittable is that the create event of the form will create a simple combobox for the cell in question.

The ability to store values within via COLFORMAT is good for predefined values, but is there a way of setting a function to call a popup in it's place?

Or alternatively, is there a way to intercept the WINMSG and call a function there?

Thanks,

Pascal

I have the same question. A combobox has the DROPDOWN event, but of course the edittable does not. This seems like something that is possible if one knows how.

Up for a response…

Hi,

I use the OPTIONS event in all edit controls, including edit-tables, to call a generic routine which displays multi-column option lists. When called from an edit-table, the utility determines the SELPOS in the table and positions the option display accordingly. Multi-column option list dropdowns in edit-tables are a natural fit, as multiple columns and rows of the option display can be selected to fill a complete edit-table in one step. SRP actually authored this utility, named popout, so you may wish to enquire there about it. Or, I will be happy to give you more information.

Thanks, Gerald. I need to talk to SRP anyway, I will ask about that.

I am using the option event also. The problem is that there is no visual clue to the user that an option is available, and Alt-Down does not seem that intuitive to an unfamiliar user. I have been asked to give some kind of consistant visual clue that an option exists for a field.

I was thinking of configuring the affected columns as dropdown comboboxes, but intercepting the message generated when a user clicks the dropdown arrow and sending it to options instead.

Of course I can route doubleclick to options, but the request here was for a consistant VISUAL clue that a field has an option. Defining the column as a combobox seemed like a way to get a bitmap that could be clicked in the column, something the edittable does not support at present. (To my knowledge.)

The edittable control's behavior seems to be the source of most user complaints, so I probably just need to replace them all with something like SRP's OLE version. At least in this application since it requires so many of them.

Jim,

I thought edit-tables were badly behaved when I started OI programming. I have since changed my opinion, but I have put in some work along the way. I use keystroke for options dropdowns (although is also enabled) so that the options key fits in the left hand along with the other standard edit keys A,Z,X,C, and V. Admittedly this is not a "visual" indicator, but it does provide a consistent user interface. You know that you can define 2 keys for a menu feature, if you just add the item to the menu twice but hide the second entry.

View this thread on the Works forum...