[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnue-dev] focus nightmare
From: |
Marcos Dione |
Subject: |
[Gnue-dev] focus nightmare |
Date: |
Thu, 5 Sep 2002 19:42:26 -0300 |
User-agent: |
Mutt/1.4i |
and I quote [typos fixed]:
[06:10] <StyXman> but the problem is that I have this nice fowm with lookups
[06:11] <StyXman> the lookips are the same entry with rows=5
[06:11] <StyXman> suppose I have no record that match my query
[06:11] <StyXman> suppose I click in the 3rd lookup
[06:12] <StyXman> suppose I start writing in this 3rd entry.
[06:13] <StyXman> the focus is 'there', even the 'cursor' (that '|' thingy)
[06:13] <StyXman> but as you write the letters appear in the 1st (!!!) entry
[06:14] <StyXman> yeap. ouch. couldn't find where to fix that[*]. I'm totally
*lost*
[06:17] <StyXman> indeed, the focus get to the last entry that
'could' be written to. in my example, as there's no matches, it goes
into 'insert' mode and writes in the first row.
[06:18] <StyXman> if I click in the 5th row, I get the same. if I
have 3 matches and try to write in the 5th, the 4th gets the data.
and so on.
[*] ok, now that's not true. I know where's the problem, but not
how to fix it. all key events goes to the form._currentEntry. in this
case, the 'currenEntry' *must* be [in] the first row, but the 'focus'
(as wx thinks of it, i.e., highlight the current widget and draw the
'cursor' in it) is in the clicked widget.
the only way I think it should be repaired is to refocus (as wx
thinks of ot) in the currentEntry.
- [Gnue-dev] focus nightmare,
Marcos Dione <=