Soon it will be delegated to Keymapping :) Thank you for the feedback :) Ben On Oct 20, 2012, at 7:41 PM, Sean P. DeNigris wrote:
In Pharo 1.4, with Spec 1.1 loaded, text widgets seem to have source code completion by default. This doesn't seem right.
Also, to set the tab order: myFieldModel isEventForNextFocusBlock: [ :evt | evt keyCharacter = Character tab ]. self focusOrder add: myFieldModel.
The block is pretty cool because it's so flexible, but it seems like most of the time, there would be one way to move through a form e.g. tab for each next field. In that most common simple case, it's a little clunky to have to specify the block for each widget. Maybe the widgets should just delegate to the parent? Also, maybe #nextFocusBlock: would be a kinder name for #isEventForNextFocusBlock: :)
Whatever we decide, I recommend adding the focus stuff to the next round of documentation, because it doesn't seem very obvious.
Cheers, Sean
-- View this message in context: http://forum.world.st/Spec-Text-Completion-focus-tp4652161.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.