Project

General

Profile

Could it be an option to disable this AdiIRC default behavior on some future release please?

Added by Eduardo Bedoya over 8 years ago

Hi, AdiIRC have many good features, and many options, but I having big troubles with this default behavior... (unfourtanely it can't be changed in the options)
When you left click on a #channel or on a nick(username) it selects it (highlighted in blue), but if you left click it again, it automatically selects the Server or #channel or nick(username) that was previously selected, I have accidentally closed #channels, and even disconnected to Server because of this behavior (left click and ctrl W). Please, I would like to always just select the item that was left clicked, no mather if it is the first or second time I click on it. Please could you create an option to disable this behavior on some future AdiIRC release?

Thanks Advanced, Thanks for your support. Congrats for the nice software.


Replies (8)

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Mr. BS over 8 years ago

What do you think do get used to SHIFT + LEFT CLICK in treebar/switchbar window item? This is the easiest way to close many windows in a row.

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Eduardo Bedoya over 8 years ago

Thanks Mr. Pereba,
I know that shortcut, but my problem is not how to close the windows,
my problem is to select the window that I want, when I select in a windows that is already selected AdiIRC selects another different windows, that's driving me crazy, is there any way to select the first private message window?? I have tried /query (1) but it open a new window called (1), I want to open the first private message window everytime, or a way to avoid selecting any #channel or any server. Thanks Advanced.

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Mr. BS over 8 years ago

Try this script, should work to bring to front query in active network:

alias query { if ($1 !isnum) { !query $1- | return } | if ($query($1)) { window -a $query($1) } }

Example, /query 1.

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Eduardo Bedoya over 8 years ago

Hi Mr. Pereba
Thanks for your support, your script worked fine, but
could you please tell me what is the difference between typing this in the main window(without creating your script)...
//query -ag $query(1)
and your script, could you please explain a little what your script does? and in what it differenciate with just typing the line above?
Thanks Advanced.

EDIT>> I have notice that in your script when I type it and there is not any private message available then it stays in the same window where it was typed, it will be nice that in that case the script will focus on any currently opened #channel (in order to avoid selecting the server window)

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Mr. BS over 8 years ago

Don't need to add -ag parameters, they does nothing in /query.

There is no difference in my script, I just added some check to trigger only when you input a number and also to fallback to regular query command in case you use a nick.

I modified the script to pick a channel in case no query is found. Also added comments to help you understand each part.

alias query {
  ; if input is not number then fallback to regular query command.
  if ($1 !isnum) {
    !query $$1- | return
  }

  ; if a query is found by input number then bring that window to front.
  if ($query($1)) {
    window -a $v1 | halt
  }

  ; In case there is no query open, then lets search for the first open channel
  if ($window(#*,1)) window -a $v1
}

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Eduardo Bedoya over 8 years ago

Hi Mr. Pereba sorry for the delay
I created your script renaming it as getPmCh instead of query like this...

alias getpmch {
; if input is not number then fallback to regular query command.
if ($1 !isnum) {
!query $$1- | return
}
; if a query is found by input number then bring that window to front.
if ($query($1)) {
window -a $v1 | halt
}
; In case there is no query open, then lets search for the first open channel
if ($window(#*,1)) window -a $v1
}
I tried your script, I typed "/getpmch 1" (without quotes) in a Server window but it only worked when there was a private msg window opened (it focus on it), cuz when there wasn't any private msg window the script showed this error...
  • $window: too many parameters (line 13, getPmCh.ini)

and did not focus on any of the two channels that were opened, it just stayed at the Server window. Am I doing something wrog??

Thanks Advanced.

PD: in my previous post I meant that I was using (and I still using) this default command...
//query -ag $query(1)
...to kinda get the same result. I just type it in any window and it opens the first query, if there isn't any, it just open and empty named query. So I can realize.

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Mr. BS over 8 years ago

I forgot to mention you need AdiIRC 1.9.7 beta, a wildcard bug were fixed.

You can type /betaup in your client for a convenient and quick upgrade.

RE: Could it be an option to disable this AdiIRC default behavior on some future release please? - Added by Eduardo Bedoya over 8 years ago

Thanks Mr. Pereba
it upgraded fine, then the script worked fine, many thanks.
But then I found that this 1.9.7 version gets disconnected from server from time to time, curiosly always after run this getpmch script, hope you release an 1.9.7 stable version. Amazing Software.
I have now perform several tests, and have found that Adi 1.9.6 run faster than 1.97 when it comes to open and close several windows consecutively.
Ill stick with my command option, Hope to hear from new Adi 1.9.7 stable version, that could handle this script to be run several times with ease. Amazing software.
Thanks

    (1-8/8)