WiiRd GUIBugs [2]1. One of the bugs I've happened to notice in the GUI version, and I'm sure it's not just me noticing it, is that after awhile of searching, the GUI freezes up. Some of the buttons work, most of the controls are still active, however, none of them actually do anything. They just sort-of sit there, holding no functionality. I would search for something, the GUI would lock-up, I'd wait, it would still be locked up, the stop buttons still works, I click it, nothing happens, I click Restart, it asks me the questions, then it would clear the search (or not) and the GUI would still be locked up.
2. WiiRdGUI's "Next" button, even when set to 60 fps, sometimes appears to step over two frames instead of just one.
Requests [7]1. Search for "Same as First". After the first scan, you are given the option to see if the value is equal to the first scan.
2. Address Container. This is an Area where you can freely poke the Addresses, and ect. It's just so that you can continue to scan without having to lose a few address. Note, this is not the GCT list.
3. Some kind of option that allows you to update the Search List values, or a selected address(es). Most likely the Context (Right-Click) Menu.
4. An Auto Updater. There is a simple way to do so. You just build in a Check that will read the latest version from a file, and ask if you would like to update. Then you download the Auto Updater, and it'll auto update for you. I've done this in many of my
bad programs.
5. A built in Float to Hex Converter for poking floating point memory cells.
6. A Step Over button above Step on the Breakpoint tab. Step Over acts just like Step, except if the current instruction is bl or bctrl, in which case it will set an Execute Breakpoint on the instruction after bl/bctrl. This will let us skip functions without having to step all the way through them. Bonus points for not over-writing the current Breakpoint field and type.
7. Memory-viewer like snapshots, for the registers as well.
Gecko dotNetBugs [2]*fixed*
1. Unable to save the Code-list for certain games. [N64] Kirby 64 (NAME). I believe this is because Gecko dotNet can not read the Game name. Gecko OS can do this though. It throws an exception at me saying that there are invalid Characters in the Path. I would assume it's because It couldn't read the Game Name.2. The GCT Code list seems like it's just a multi-line Textbox. When you edit codes, they like to mess up and bring codes from the line above where you were editing down, and it's a little bit of a hassle to bring them back up.
*fixed*
3. When you play certain games (Like [N64] Kirby 64 (NAME)), the Notepad breaks, and throws an Exception saying Illegal Characters in path.4. GeckoDotNet's Auto-starting Gecko OS does not appear to work. It doesn't even initiate the countdown or start loading the game. You need to start Gecko form the Wii.
Requests [6]*done*
1. Being able to step-through the frames in a game with the Pause Button. In WiiRd GUI, when you pause a game, you can click "Next" and it'll step through the frames.*done*
5. A Step Over button above Step on the Breakpoint tab. Step Over acts just like Step, except if the current instruction is bl or bctrl, in which case it will set an Execute Breakpoint on the instruction after bl/bctrl. This will let us skip functions without having to step all the way through them. Bonus points for not over-writing the current Breakpoint field and type.1. "Same as first" search type. This would be added after you make the first scan.
2. Being able to Manually Update the Value of an Address (not the Watch-List) in the Search List, or whatever one you choose. This can be done with the Context (Right-Click) Menu.
3. When you want to capture a Screen-Shot, You should have the option to choose where yo want to save them to, and as what file name (not file type).
4. A built in Float to Hex Converter for poking floating point memory cells.
5. An Auto Updater. There is a simple way to do so. You just build in a Check that will read the latest version from a file, and ask if you would like to update. Then you download the Auto Updater, and it'll auto update for you. I've done this in many of my
bad programs.
6. Memory-viewer like snapshots, for the registers as well.
These are just my Bugs/Requests I've come across/came up with. If you guys feel something is wrong, or want to add your own, post here and I'll gladly add them.
Fixed [3]1. Some-how speed up the Search speed to atleast the same speed as WiiRd GUI.
This was added into the latest Update of gecko dotNet Version 0.4
-block based search refining - VERY fast (outbeats WiiRd in most if not all situations)
2. Unable to save the Code-list for certain games. [N64] Kirby 64 (NAME). I believe this is because Gecko dotNet can not read the Game name. Gecko OS can do this though. It throws an exception at me saying that there are invalid Characters in the Path. I would assume it's because It couldn't read the Game Name.
3. When you play certain games (Like [N64] Kirby 64 (NAME)), the Notepad breaks, and throws an Exception saying Illegal Characters in path.
Both of the above are fixed now.
2. Should be finally fixed (it actually copied null byte characters into the string)
3. Should be fixed along (also null-byte issue)
Possible Solutions [1]An Auto Updater. There is a simple way to do so. You just build in a Check that will read the latest version from a file, and ask if you would like to update. Then you download the Auto Updater, and it'll auto update for you. I've done this in many of my
bad programs.
The way I did it, was after 5 seconds from the program starting up, I created a new webclient, then downloaded a string from a text-file (lol I know), the string was a double, showing the current version (example: 0.61), if it was greater than the programs current version (a public double) it would tell you updates are available, and ask if you would like to update. If you said yes, it would check to see if the program called: "AutoUpdater.exe" was in the directory as the program, if not, it would download it, and when it's done downloading it, it would launch it, and close it-self. The AutoUpdater.exe would not do anything until the program was closed (process.exe). When it was closed, it would go online, and download a string containing all of the updates, and where to download them. After it finished downloading all of the updates, it would launch the process and it would be updated.
