Hi

on TABCOMP is a great event, but it only works if there is a text on the editbox (right?). What if it also got triggered when the editbox was empty (but selected)?

Thank you,
Zyzzy.

it does

It triggers when the tab key is hit, no matter what it is in the editbox.

It doesn't here. Selecting the editbox and hitting the TAB won't do anything.

on *:tabcomp:*: echo -s * test

Is there something I'm missing?

Your exact line was tested and worked fine. You might have remotes off? or your nit running mirc 6.20 LOL!

I've got no idea what I'm doing wrong, or maybe I'm not being clear enough Using the line above, clicking on the editbox (empty) and hitting TAB won't do anything. Only if something is typed there it will work, including the hard space $chr(160).

I'm lost =P

no your being completely clear, thats exactly what i did and it did work.

on TABCOMP should trigger even in an empty editbox. Which version of Windows are you using?

I'm using XP Pro SP2

One thing I noticed is that the "empty TAB" does work with a clean, script-free mIRC 6.2; but it does not work with my usual mIRC - with my scripts and everything else. I've even tried loading the ON TABCOMP as a separated remote, without success. I wonder what type of script could be preventing the event from being read.

Weird..

Well start taking things out, untill u find the one that cuases it, then report back on what u find, rather than giving missleading reports that it "just doesnt work".

I did what you suggested and unloaded all remotes, aliases, variables, userlist, popups and guess what? It still won't work

The only apparent difference between the 2 mIRCs (the working and the non-working), are the options and the background/font colors

lol, sorry to hear that, seems pretty wierd, do u experence this in all windows?

//window @ex -el @ex | aline -l @ex abc | aline -l @ex def

test on a custom window maybe?

Custom windows, status window, channel windows, query windows.. nothing *head scratch*

I tried doing the reverse process, and loaded my scripts one by one, to see which one hatled the ON TABCOMP. Again, nothing.. after all scripts were loaded, the TAB still worked

Does anyone else can verify this?

Thanks for the help, I think I may have figured it out... do you have the "Tab key changes editbox focus" option enabled in the Options/Other/Keys dialog? If I enable this option I can reproduce the problem.

If this option is enabled and the Tab key is pressed in an empty editbox (or in a situation where tab completion is not necessary), mIRC changes the focus to the next editbox/listbox. Triggering the the TABCOMP event in this situation did not seem appropriate.

I will add a note to the on TABCOMP section in the help file describing this situation.