@BullyWiiPlaza Would you change the button field in the codes tab to static so it doesn't increase/decrease its height when you have a larger/smaller code selected?
I'm not sure if this is possible because it's controlled by the layout manager but I will try.@BullyWiiPlaza Would you change the button field in the codes tab to static so it doesn't increase/decrease its height when you have a larger/smaller code selected?
This doesn't really happen, all address accesses are checked. Otherwise you can't even jump by double-click. Try it out.1. Add a Check before going to an address in the memory viewer with a double click, to make sure the address is in the games range before going to it. (To prevent DSI crashes from accidental double-clicks)
This doesn't really happen, all address accesses are checked. Otherwise you can't even jump by double-click. Try it out.
The A0000000 range is allowed to be accessed but it also crashed a lot for me lately so maybe I'll block that also.I see now. I thought it was a signed integer issue originally. From what i can tell, it seems like addresses that start with a letter are not handled and the jgecko still tries to jump to them.
i tested up to address 90000000 and it worked fine until A0000000. I guess every time it happened to me, it was probably just bad luck that i double clicked on a negative floating point value.
Done.@BullyWiiPlaza Would you also add frame.setLocationByPlatform(true); so the OS can decide where it will show the window? Having it in the center is a little bit inconvenient if you don't have a high resolution because half of the window is outside of the screen.
I added an additional OSIsAddressValid() call so accessing ranges is less likely to crash despite them being in the kernel address table.I see now. I thought it was a signed integer issue originally. From what i can tell, it seems like addresses that start with a letter are not handled and the jgecko still tries to jump to them.
i tested up to address 90000000 and it worked fine until A0000000. I guess every time it happened to me, it was probably just bad luck that i double clicked on a negative floating point value.
I'm not sure if this is still relevant, does it still happen in the latest build now?Would you change the button field in the codes tab to static so it doesn't increase/decrease its height when you have a larger/smaller code selected?
Fixed.2. There is a an out-of-bounds array exception that occurs when typing a Return/Enter character or sometimes pasting assembly in the Assembler. It would be nice if that didnt happen.[/USER]
Also fixed.3. When Results are deleted from the results list, remove them entirely. Right now, if you refresh results or perform another search, all of the deleted results return, and they shouldnt.
Done but without checkbox. It's now like that by default.4. When performing an Equal search, if the new values are the same as the Current Value from the last results, keep the Previous value the same as they were before. Essentially Previous Value and Current Value should never be equal. This would make it nicer to see changes when mass poking Previous and Current values. If the Current and Previous values are the same, its useless to poke the previous value since it is not different and you wont see a change.
It's still in latest build. If you select a small code thats only 2 lines long it will increase to its maximum, when you select a long code that goes to the bottom it resizes itself to its minimum.I'm not sure if this is still relevant, does it still happen in the latest build now?
Follow the first post again exactly like it says.i ran cosmocourtney codehandler i ran breath of the wild
i ran jgecko u
but breath of the wild chashes saying illegal command, how do i fix that? i'm in 5.5.2 so i can't run kernel and stuff
It's still in latest build. If you select a small code thats only 2 lines long it will increase to its maximum, when you select a long code that goes to the bottom it resizes itself to its minimum.
I never got this and I spammed the checkbox on/off. The function is synchronized so it doesn't have race conditions. Since it didn't happen to me once and I don't know the exact error stack trace I scratch that off my list also I guess.I also get sometimes when I check or uncheck a code a FileNotFound exception for the archive.zip in the codes folder.
Yes like with regular poke.Also Poking Previous Values now changes all the Current Values to the previous values. lol.
Yes like with regular poke.
But you don't like that?