mIRC Homepage

Compiled thread...

Posted By: trenzterra

Compiled thread... - 11/09/03 02:23 PM

To make Khaled's life easier, I've decided to make a new thread listing all the important bugs in mIRC 6.1 that needs fixing... all these bugs have gotten me fed up...

1. Colour buggies:
-after colour code 15, all colours are messed
-can't change colour using /color

2. /hdec as /hinc
-link

3. Popup buggies
-menu bug
-use your keyboard, and pfft... nothing works

I'll add more later... if you think something needs to be fixed too, post it here...
Posted By: Bilge

Re: Compiled thread... - 11/09/03 03:26 PM

If there is going to be a new version soon to address these issues, then I would request another 'fix'. When you have regex as match text in an event definition, example:
$*:text:/someregex/:#: { ... }
the regex is severely limited in power. For example, the following pattern constructors do not work:

(?#) - inline comment
(?:) - non-capturing groups
And based on this trend, I would assume that constructors like zero-width negative look-behind assertions do not work either: (?<!), and other assertions such as (?=), (?!) and (?<=). However, I havn't tested assertions.

I don't feel there is a need to, because I am requesting that the regex used for match text in an event defition be as powerful as the regex support exported by the $regex identifier. This would be much more flexible and hence much more useful. It would also be potentially quicker, because non-capturing groups are processed faster than capturing groups.

Finally, the list of scripts available from the view menu in the mIRC Scripts Editor now only shows 24 scripts and a "More..." option. This is quite annoying, and I assume it was provided as a quick fix to the problem of there being so many scripts that they didn't fit in the display area. Perhaps Khaled could sort us out with one of those arrows at the top/bottom of the menu to scroll the list of scripts?

I think I'll stop there to spare this thread a rant!
Posted By: Matteh

Re: Compiled thread... - 11/09/03 03:47 PM

The Issue with mirc crashing when handling .pngs...
Posted By: Rich

$highlight().color bug - 11/09/03 04:53 PM

The $highlight().color bug:
$highlight().color always returns the color+1

Reproduction:
  • Go to Tools>Options>IRC>Highlight
  • Press Add
  • Type blah in the top editbox
  • Select the bottom color from the Color combo
  • Press OK
  • Press OK
  • Type //echo -a $highlight(blah).color

It echoes 16 instead of 15

This happens for any color, not just 15
(I believe this has been posted before, but because I couldn't find it I assumed the post has been torched.)
Posted By: codemastr

Re: Compiled thread... - 11/09/03 09:48 PM

Here is a list of every bug I've seen reported in 6.1 that I was able to confirm myself:

-/qme and /qmsg think they are /ame and /amsg
-/fopen creates a file even if -n isn't specified
-The colors dialog reverts the scheme after /color is used
-$decompress can crash mIRC and/or the entire PC
-$duration(N,3) screws up with large numbers
-/setlayer no longer can make mIRC transparent
-The right alt key no longer functions
-ctrl+break and ctrl+scrollock don't work correctly under WinXP
-$os returns .NET instead of 2003 for Windows Server 2003
-Paste confirm option incorrectly counts lines in a paste
-Dynamic menus (submenus) are completely broken
-"grayed text" was renamed "gray text" breaking all MTS themes
-Color codes > 16 are no longer parsed (N % 16) instead it just displays black
-Using the favorites dialog to join a channel you are already in makes the active window update, but not on the switchbar
-/hdec actually increases rather than decreases
-Multiline comments (/* */) don't work correctly if placed on a single line
-$fopen produces an error when given a file that is not opened
-Received files folder toolbar icon doesn't update if you change the received folder (for sounds) via alt+o, drop down menu will still say $mirddir\sounds
-Can no longer select multiple channels from the favorites dialog
-SOCKS proxies no longer seem to work (resolver problems)
-$fline with regex support always does a case insensitive comparison
-$base incorrectly rounds when converting using floating point
-$dllcall/$comcall crashes if given 3 parameters
-$comcall seems to always freeze even when the same operation using $com works fine
-/fwrite -n incorrectly reports the number of bytes written to the file
-Active "dot" on script editor toolbar button does not function as described
-/fopen -n deletes all text in an existing file
-Identifier warning feature incorrectly reports that $event does not exist when used in an alias that is called from an event
-Pressing the space bar to activate the nicklist menu causes the menu not to function
-$highlight(N).color returns the color +1
-Pressing f in a window that has no editbox no longer triggers the find dialog
-PNGs crash mIRC
-Topics are still truncated
Posted By: Bilge

Re: Compiled thread... - 11/09/03 10:45 PM

Quote:
Multiline comments (/* */) don't work correctly if placed on a single line

Although the help file is not precise about this, versions.txt is. This is a quote from versions.txt:
Quote:
84.Can now use /* and */ to comment out multiple lines in an alias,
popup, or script. Each be used alone on a single line.

Speaking of the help file and comments, in this portion of the help file there is a typo.

Quote:
You can add comments to your scripts by using the ; semi-colon at the start of a line, or /* and */ to enclose test.

Should read "text" instead of "test".
Posted By: trenzterra

Re: Compiled thread... - 12/09/03 01:29 AM

Yes, and...

Only able to select one option in mIRC Favourites
$fread happens twice when there is an empty line, returns two empty lines
Posted By: cold

Re: Compiled thread... - 12/09/03 10:52 AM

Quote:
$fread happens twice when there is an empty line, returns two empty lines

It seems to work fine here, as I said in your thread.
Posted By: pheonix

Re: Compiled thread... - 12/09/03 05:41 PM

Quote:
-$fopen produces an error when given a file that is not opened

still a bug but, its simple to fix:
Code:
if ($fopen(0)) &amp;&amp; ($fopen(name)) {
Posted By: Raccoon

Re: Compiled thread... - 12/09/03 05:49 PM

Nope. Same error persists if 'name' doesn't exist.

* Invalid parameters: $fopen
Posted By: pheonix

Re: Compiled thread... - 12/09/03 05:51 PM

worked fine for me crazy
Posted By: Raccoon

Re: Compiled thread... - 12/09/03 07:06 PM

Only because you failed to have any files opened.

Imagine having 10 scripts going, each with a dozen different files opened, so that $fopen(0) == 120

if (120) && ($fopen(something)) echo -a YEP!

* Invalid parameters: $fopen
Posted By: codemastr

Re: Compiled thread... - 12/09/03 07:41 PM

Quote:
Although the help file is not precise about this, versions.txt is. This is a quote from versions.txt:

84.Can now use /* and */ to comment out multiple lines in an alias,
popup, or script. Each be used alone on a single line.


Khaled has a typo there, it says "Each be used" you assume that should have said "Each MUST be used" I assume it should have said "Each MAY be used" simply because, according to Khaled, mIRC scripting resembles C/C++ (he said that, not me) and in C/C++ there is no restriction like that, all of the following are valid:
/* this is
a comment
*/
/* this is a comment */
/* this is
a comment */
etc.

So until he clears that up, I'd say it's a bug.

Posted By: Bilge

Re: Compiled thread... - 12/09/03 11:05 PM

Actually I assumed it was supposed to say "Each TO be used". Anyway, I would agree it's ambiguous, both in versions.txt and in the help file, and the bad grammar and typos don't help.
Posted By: Raccoon

Re: Compiled thread... - 13/09/03 01:22 AM

I think the grammar/ typos in both sources are too perfect to be accidental.

This has to be some sort of test Khaled and Tjerk are playing on us.
Posted By: qwerty

Re: Compiled thread... - 13/09/03 02:38 AM

Regarding the regex support in events, it supports all features $regex() does. The problem is with special characters like "{" , "}" and ":". Since ":" is used as a delimiter in the event header, you can't use the (?:) item because the parser doesn't know that the ":" char is actually a part of the regex. Similarly, \d{1,2} can't work. Negative/positive lookaheads/lookbehinds (and anything else that doesn't contain these special characters) work fine.

I'd like to see a method of getting around these issues, although I imagine it won't be that simple.

Regarding the mirc Editor showing only 24 items and More..., I totally agree, it has to go.
Posted By: starbucks_mafia

Re: Compiled thread... - 13/09/03 10:22 AM

With the $ prefix you can use $() in the matchtext event or if you supply a variable it will automatically evaluate it (on $*:text:%moo:*:commands).
Posted By: qwerty

Re: Compiled thread... - 13/09/03 11:28 AM

Yeah, this works but kinda defeats one of the purposes of the $ event prefix, which is to avoid the evaluation of identifiers/variables. The %variable way is probably the fastest workaround, but... it has to be a global variable, not a pretty solution. $($mypattern) in the header works too, but now the overhead is very close to that of /if ($regex($1-,<pattern>)) in the event body.
Posted By: Bilge

Re: Compiled thread... - 13/09/03 06:38 PM

Well since the // are required at the start and end of the matchtext, and these characters are not valid for the next parameter (where the text matches, i.e. in a channel or whatever) then there should be no reason why these symbols are not allowed for regex matching.

Oh, and at the start of this thread, mIRC bug #2 about /hdec working as /hinc which was posted by me has been graciously deleted without notice. Regards to whoever did that.
Posted By: trenzterra

Re: Compiled thread... - 14/09/03 06:15 AM

Ok... for /hdec it should be this url then:

here
Posted By: lordares

Re: Compiled thread... - 14/09/03 06:10 PM

dont forget $md5 has never worked apparently with '%' in the text

link
© 2022 mIRC Discussion Forums