RE: [platform-swt-dev] Overrriding default behaviors

["Erik Poupaert" <erik.poupaert@xxxxxxxxx>]

>>>>> We are trying to add editing capabilities to the Table widget. We
would
>>>>> like to simulate the Excel's cell behaviour, including the "embeded
>>>>> combo" option. The problem is some keys already have behaviour that we
>>>>> cannot override (la arrows chang the selection in the combo). We'd
like
>>>>> to allow the user to use the keys to navigate through the cells but we
>>>>> cannt avoid the combo selection to change (in the case of the up and
>>>>> down arrows).
>>>>> That default behaviour doesn't do any harm in the case of the Text
>>>>> widget, it just moves the cursor.
>>>>> So, is there any way, including subclassing or calling the OS, to
avoid
>>>>> the widget's default behavoiurs envolving the key events?

This fits perfectly well in the general problem that framework builders are
usually never involved in the vertical, end-user applications that will use
the frameworks; so, they won't know that the following things are essential:

GUI:
(1) editable grid
(2) multicolumn combos

Language:
(3) dates: primitive date type with good date support (no months from 0 to
11, please!!! do you hear me, Sun?)
(4) amounts: primitive fixed point type (you can't do money calculations
with floating point types; do you hear me, Sun?)

Instead, they keep on adding things that they think are interesting, but
which have little or no use in vertical applications.