[EMAIL PROTECTED] (Tony) wrote in message news:<[EMAIL PROTECTED]>...
> > So you disabled key navigation and reimplemented it? > > Well, yes. I did have some doubts about what I was doing at the > time, but it just didn't seem to be doing what I needed - maybe it was > the time delay that gave it a problem, I'm not sure. I certainly > thought it was going to do the job for me and was disappointed when it > didn't seem to work out - maybe I was doing something wrong. All I > was getting was matching on the first character with each keypress. I > will look at it again when I get a few minutes. > > I have actually got keynavigation to work in another example, although > this one seems to be on strictly the first 2 characters which is what > I what - in this instance the third character is always a space. I > did read somewhere where the timeout can be set but I cannot now > re-locate it. Apologies for posting on my own post, but I have now taken a look at this again. It was, indeed, the automatic timeout that the standard keynavigation did that I was not happy with, it seems a bit on short side if the user is entering alphanumeric codes and I could not find a way to extend it. Maybe I missed something, there is a timeout attribute for a textbox but I have not found one for a tree. The other little nicety that my own code has, is that it scrolls the selected line to the middle of the box rather than leaving it at the bottom. But, I must admit, I am not generally in favour of re-inventing wheels and I would revert to the standard one if I could solve these issues. _______________________________________________ Mozilla-xpcom mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpcom
