mIRC Home    About    Download    Register    News    Help

Active Threads | Unanswered Past 24 hours | Past 48 hours | Past Week | Past Month | Past Year
Bug Reports Jump to new posts
Re: Editbox option 'optional' Khaled 37 minutes ago
Yes, that sounds about right. Let's see how the next beta works out.
3 18 Read More
Bug Reports Jump to new posts
Re: Editbox option 'optional' TECO 1 hour ago
Originally Posted by Khaled
Thanks for your bug report. This is a bit more complicated than I anticipated. The (Optional) text has always depended on whether the editbox has focus or not. But in the case of custom dialogs, scripts can modify the content whether the editbox has focus or not. The only way around this that I can think of is that if a script tries to modify the editbox in any way, the (Optional) indicator will be automatically unset. And if a script tries to get the contents, it will return an empty value. This change will be in the next beta.
Hi,
In my opinion, when I requested the addition of this condition, it was so that when the edit box is empty, the text (Optional) would appear, and when it is focused and the cursor is present, the text would disappear so that something could be typed. However, if you want to keep the edit box empty, the text (Optional) would still be displayed, but when you click OK, $did(name,id) would not return anything.
3 18 Read More
Bug Reports Jump to new posts
Re: 7.82 broke login via nickserv on connect? deVilbaT 1 hour ago
In the latest beta version, the bug has not been completely fixed. In the Edit Server window (Options), set the login method to /msg nickserv or /nickserv, then fill Username and Password fields. Unfortunately, mIRC sends this data incorrectly. It only sends the Password (verified in @debug). However, when we fill in only the Password field in the following way: <username> <password>, the data is sent correctly.
4 280 Read More
Bug Reports Jump to new posts
Re: Editbox option 'optional' Khaled 4 hours ago
Thanks for your bug report. This is a bit more complicated than I anticipated. The (Optional) text has always depended on whether the editbox has focus or not. But in the case of custom dialogs, scripts can modify the content whether the editbox has focus or not. The only way around this that I can think of is that if a script tries to modify the editbox in any way, the (Optional) indicator will be automatically unset. And if a script tries to get the contents, it will return an empty value. This change will be in the next beta.
3 18 Read More
Feature Suggestions Jump to new posts
Re: (optional) text in the dialog edit field Wims Yesterday at 11:20 PM
Couple notes.

Your suggestion is great and is an obvious improvement upon the original, too simple, suggestion.
But what you proposed syntactically speaking doesn't work: if you want an optional text for the editbox then you wouldn't be filling AND a ghost text AND the original field for the editbox's text.

The new beta only implements a default (optional) text, which, practically speaking, is quickly limiting, a better implementation which doesn't break the current syntax would be

Quote
edit "", id, x y w h, ... optional
With the optional option and empty value for the text, it would then show the default (optional) as an optional/ghost text.

Quote
edit "custom", id, x y w h, ... optional
Whereas this would then show the custom optional/ghost text "custom"

And we do need a /did switch to get that behavior.




It would also be nice to have an option to get a default value, so basically a text that is selected, which, when in focus, would automatically overwrite itself.
This can't be scripted.
2 278 Read More
Feature Suggestions Jump to new posts
Re: ARM64 Support for mIRC Jinx_Dojo Yesterday at 08:25 PM
As of 2025/11/06, the beta post notes:
Quote
3.Updated code to clear all remaining minor static code analysis issues
reported by the compiler. This will make it easier to spot unhandled
issues in the future across 32-bit/64-bit/ARM64 versions.

However, that post/page is transitory in nature and so is often blank. Fortunately, versions.txt is persistent and also notes it (emphasis added):

Quote
8.Updated all external libraries to support compilation as both 32-bit
and 64-bit, in preparation for a future 64-bit release and possible
ARM64 support
. Updated all routines to use 32-bit/64-bit compatible
types, performed static code analysis, compilation and testing under
different Visual Studio versions, SDKs, and platform toolsets,
focusing on common 32/64-bit porting issues, with the aim of
minimizing code changes and hardening code.

(It doesn't look like a 32-bit ARM is planned, so those of us with RaspberryPi 2 servers are out of luck!)
4 2,567 Read More
Bug Reports Jump to new posts
Editbox option 'optional' TECO Yesterday at 01:55 PM
Hi Khaled,

Thank you for adding my suggestion.

However, I'd like to see if this is a bug or the intended behavior. When I have the "optional" condition for the edit box, and if I don't type anything and click OK, it's normal for the identifier $did(name,id) to return the text (optional).

Example:

[Linked Image from i.ibb.co]


Code
dialog version {
  title "Version"
  size -1 -1 306 155
  edit "Enter the server or nickname:", 1, 10 12 290 60
  edit "NOTE: If empty it will query the current server.", 2, 10 71 270 16, disable
  edit "", 3, 8 92 290 22, autohs optional
  button "&OK", 4, 142 124 76 23, ok
  button "&Cancel", 5, 223 124 76 23, cancel
}
on *:dialog:version:{
  if ($devent == sclick) && ($did == 4) { .raw version $did(3) }
}

Return: ".raw version (optional)"

The only solution I see is to put $remove($did(name,id),(optional)) in the command.

Example:
Code
.raw version $remove($did(3),(optional))

3 18 Read More
Bug Reports Jump to new posts
mIRC beta Khaled 03/11/25 03:34 PM
The latest beta can be downloaded here and includes the following changes:

Quote
Beta 7.82.526 changes:
1.Item 1, fixed.
2.Item 2, added.
3.Item 3, updated. These are minimal code changes that clear up minor
warnings for specific sections of code.
4.Item 4, added.
5.Item 5, fixed. The code was being used in different contexts, so I
have changed it to be more strict. Unit tests across different
features where this is used seem to be working correctly.
6.Item 6, fixed. This was reported for the Options dialog listbox but
I was not able to reproduce it. However, code was changed that relates
to listbox line heights, so has been changed to work as before.

Changes:
1.Fixed nickserv logon bug where the message was not being sent on
connecting to a server.
2.Added support for key derivation functions pkbdf2 and argon2 as
identifiers:

$pbkdf2(text|&binvar, salt|&binvar, hash, length, iterations, opts)

$argon2(text|&binvar, salt|&binvar, hash, length, iterations,
parallelism, memcost, opts)

The opts parameter is optional and can be set to 'b' to indicate
&binvar parameters. The return value is the derived key.

3.Updated code to clear all remaining minor static code analysis issues
reported by the compiler. This will make it easier to spot unhandled
issues in the future across 32-bit/64-bit/ARM64 versions.
4.Added custom dialog editbox option 'optional' for grayed out optional
text indicator.
5.Fixed IPv6 parser change that affected a number of features, such as
the /dcc send/chat commands with nicknames that contain brackets.
6.Fixed listbox font height not being set correctly for some features.
1 447,766 Read More
Bug Reports Jump to new posts
Re: 7.82 broke login via nickserv on connect? Wollino 02/11/25 06:33 PM
Hi! I can confirm that this annoying bug is present in this version. But I'm SURE that the Father of mIRC will fix this and other issues encountered with this update as soon as possible.

Thank you, Khaled, for always working to improve mIRC.
4 280 Read More
Feature Suggestions Jump to new posts
Re: Drag & Move Channels Wims 01/11/25 05:56 PM
Being able to drag and move channels around has been suggested a lot before.

Being able to see emoji is a font issue and mIRC does fallback to different fonts when a character isn't available in a font so you should be able to see emoji, you can try to set your font to 'segoe ui'.

As far as using emoji you can use this script which lists all the 'face' emoji in a custom windows, double clicking copy to clipboard.

alias emoji {
if ($window(@emoji)) { window -a @emoji | return }
else {
window -odl @emoji -1 -1 100 500 verdana -28
var %a 1,%l 128512 128515 128516 128513 128518 128517 129315 128514 128578 128579 129760 128521 128522 128519 129392 128525 129321 128536 128535 9786 128538 128537 129394 128523 128539 128540 129322 128541 129297 129303 129325 129762 129763 129323 129300 129761 129296 129320 128528 128529 128566 129765 128566 128527 128530 128580 128556 128558 129317 129768 128578 128578 128524 128532 128554 129316 128564 129769 128567 129298 129301 129314 129326 129319 129397 129398 129396 128565 128565 129327 129312 129395 129400 128526 129299 129488 128533 129764 128543 128577 9785 128558 128559 128562 128563 129770 129402 129401 128550 128551 128552 128560 128549 128546 128557 128561 128534 128547 128542 128531 128553 128555 129393 128548 128545 128544 129324 128520 128127 128128 9760 128169 129313 128121 128122 128123 128125 128126 129302
while ($gettok(%l,%a,32)) {
aline -l @emoji $chru($v1)
inc %a
}
}
}
alias chrU {
var %chr = $iif(U+* iswm $1, $base($mid($1, 3), 16, 10), $1)
if (%chr isnum 65536-1114111) return $chr($calc(55232 + %chr / 1024)) $+ $chr($calc(56320 + %chr % 1024))
return $chr(%chr)
}
menu @emoji {
dclick : clipboard $sline(@emoji,1)
}
1 99 Read More