Searching bug and suggestion.

[high6]

well first the bug. if you try searching Char(1 byte) and use a non hex or decimal value it will give u an error. now my suggestion is add string searching support and searching for selected and all.(like artmoney has for options.)

[L. Spiro]

well first the bug. if you try searching Char(1 byte) and use a non hex or decimal value it will give u an error

A char is a number.
Enter the same value as you would for a byte, but negatives are allowed.
The next version will allow entering char values as characters as alternatives.

now my suggestion is add string searching support

It has had string search for years (and unlike ArtMoney you don’t need to pay for it).

and searching for selected and all

What?


L. Spiro

[paul]

A char is a number.

I thought a char was a character, but since you have to store them in a buffer, the number you searched for was the buffer..

[L. Spiro]

Programmatically speaking a char is just a signed byte.
Or rather, a byte is an unsigned char.

So char is just a number like a byte, but can be negative instead.


This was my earliest coding, and back then (6 years ago) I was thinking more in programming terms.



As it is known, I have begun remaking the entire project from scratch and this time through I am basically fixing all the tiniest mistakes I made in the original.
This would be considered one of those tiny mistakes.

The next release will treat the character type as an actual text character, complete with escape sequences for extended characters (for example, “\n” or “\xFF”).



The String Search has been redone as well and also allows escape sequences now, along with the additions of Wildcard and Regular Expression searches, and options such as matching case and whole word only.


L. Spiro

[esco]

I don't know if it's just me but is anyone else having a problem using the sub search option changed by?

example: an enemy has 480 HP... I hit it and it takes 13 damage... so I choose subsearch- change by and it says NO results found... but if I just pick the option for decreased instead, it WILL find it... AND it HAS decreased by 13. VERY WEIRD!!! I figure that this has to be a bug.

[L. Spiro]

Did you enter -13?


L. Spiro

[esco]

Did you enter -13?


L. Spiro

Honestly no, I figured that it just needed the value amount it had changed by.... I never thought of that... that's a brilliant way to incorporate things... I'm assuming it can also do x and / right (though I don't see how this would be much use, but I'm just curious)? No need to answer, I'll have to try this on my own. Thanks.

[esco]

Well I tried entering (-)13 under changed by... it doesn't work Spiro... so I'm assuming this has to be a bug right? I even had the value to the left so I could see it changing myself... it still didn't find it.

[L. Spiro]

No parentheses.


L. Spiro

[esco]

No parentheses.


L. Spiro

I didn't use parenthesis... but I saw your other post and from you said it has something to do with the fact that my initial search is in unsigned short (2 bytes) right?

[L. Spiro]

It shouldn’t make a difference; it just uses integer overflow to add back into the negatives.

You can try a signed short instead anyway.


L. Spiro