I have no problem with core functionality I only have trouble understanding the things i talk about.
If you have to read documentation to understand how undo works and why it doesn’t then its bad design.
Ctrl + Z should always be undo Ctrl + F should always be find, CTR + C copy CTR + V paste CTR + A select all.
I don’t care in what window I am working, it’s just how things are everywhere and everyone knows about them.
I have no interest in going personal with this as you just started about my inability to reverse engineer how undo works it’s just sad to be reading that. It turns out docs are lacking in all places in all projects, for ex. there’s lack of examples of how to use certain IDA APIs from Python even that they are documented good luck spending 3 days to understand how to call them. Especially for someone who is new in the RE field.
I am only interested in better functionality and easier-to-use tools all over the place. What does it change if the tool was made in 199X ? It still has a ton of space to improve and I am pointing these places from my understanding and my usage. It’s in the developers and owners and users best interest to keep improving.
I understand Your frustration especially if You just began but You didn’t even provide anything more than “I don’t like it”. I didn’t want to attack You personally but I find it amazing that in such day and age, access to AI people ask why undo doesn’t work like in other apps. My argument about program being old is not that there’s no room for improvement, but think about it like that: the amount of source code IDA has is probably astounding. Many people are actually very familiar with it and wouldn’t like to change anything in that regard. Now what makes more sense: spend X amount of time (massive amount of time, let’s be honest here) to rebuild the things You don’t like, irritate most long time users that are already familiar with the workflow and potentially introduce yet another pack of bugs or focus on developing the tool further and fix existing bugs ? I think the answer is clear. I feel like the problems You’ve encountered are Your problems not necessarily IDAs fault.
Thank you for the script. It does take a pretty long time to scan the whole process memory for strings, but after the list appears (with 162035 items in my case), I do not observe freezes on Ctrl-F. Could you upload a screencast?
I will write better script in my free time, probably the strings are not so similiar so filtering have no problems.
I will reply with this later.
But for now as you can see IDA freezes the main thread when searching for strings, when filtering it also can freeze it. Meaning the strings implementation works on the main thread.
I still can’t reproduce but I know how to fix this for now.
There should be an option to “cancel” the search.
This is what i get when search is going, the only option is to restart IDA… bad design.
Strings window is unusuable while debugging and I have no idea where to look for logs to know what is happening.
Trying to rebuild the strings takes ages when debugging too.
it’s just sad to be reading that. It turns out docs are lacking in all places in all projects, for ex. there’s lack of examples of how to use certain IDA APIs from Python even that they are documented good luck spending 3 days to understand how to call them. Especially for someone who is new in the RE field.