Gecko dotNET release thread (version 0.65 now!)

[IRS]

well fine then just go and make the best tool ever why dont you :P and dang you are good at it too lol

[dcx2]

test build r102

- increased Memory Viewer Search character limit to 256
- added Hex to Memory Viewer Search Types (good for finding unique Z values for F6 codes!)
- Added "Copy Function" to Disassembler context menu.  This will try to put the whole function into the clipboard, instead of just the visible disassembly.

Has anyone been testing these features (Serial Poke, Step Out context menu, Disassembly search)?  I see there's about 5-10 people who appear to be downloading the test builds.

[Bully@Wiiplaza]

I am one of them, but haven´t tried out these features yet.
Can´t explain it well now. :confused: I selected multiple adresses and clicked serial poke and it gave me an error.
And thanks for adding more characters search, worked fine :p

[dcx2]

test build r103

- Added HistoryTextBox to Disassembly selected address value
-- When Assemble is clicked, it stores the original address/ASM in the history for you automatically; double-click to show so you can "undo" your ASM edits
- Added SRR0 != and SRR0 == to Show Mem Context Menu
- Added Show Mem Context Menu to Step Into and Step Over
- Changing the Show Mem Context Menu value will poke

I know some people have asked for ASM edit history.

I think wiiztec wanted those last three near the Step buttons so you don't need to move the mouse as much while stepping through.

[dcx2]

test build r104

- Added "Regex Search" checkbox to About tab
-- When Regex Search is unchecked, the Disassembly Search is literal, so you don't need to escape it
-- So (r29) would match (r29)
-- When Regex Search is checked, the Disassembly Search will use Regular Expressions
-- So \(r29\) will match (r29)

Since regular expressions are difficult for even most programmers, I decided to make the search simpler, with the option of using regex for those who can use it.  The default is Regex Search unchecked.

[dcx2]

test build r105

- Fixed bug where disassembler would crash when assembling an instruction that was less than 8 characters
-- This bug was introduced with the disassembler history and did not affect previous versions

[dcx2]

test build r106

- when a code is entered into the GCT textbox that does not have enough hex digits, it will pad 0s instead of returning a blank code (fixes one a Bully bug)
- when a code is entered into the textbox and then immediately dragged, it now updates the code before beginning the drag (fixes another Bully bug)
- when dragging a code, the dragged code remains selected when the drag completes; previous behavior had no selected codes after drag completes (this one's on me! ^_^)
- fixed case insensitive Memory Viewer search; previously, only the case sensitive searches would work (third Bully bug)

I'm not ignoring requests.  But it's a holiday weekend in the US.  I will get to them later.  For now, here are bug fixes.

[dcx2]

test build r107

- Added Memory Viewer Font Size text box to the Memory Viewer Grid Context Menu (for Bully)
- Memory Viewer Grid cells now automatically resize to show their contents without an ellipsis (for spunit)
- Added View Floats as Hex checkbox to the Show Mem Context Menu (for ZiT)
- When using GCT Wizard on a Search Result, the address/value from that result will be loaded into the Wizard automatically (for Bully)
- If the Search Comparison Value text box is empty but also disabled, the Search will still continue (for Bully)
- When using the GCT Wizard from a context menu, it will load the code that is currently selected in the GCT Code tab.  This makes it easier to "build" a code one line at a time by leaving it selected when you leave the GCT Code tab.  To make the wizard load a New Code, make sure no code is selected

[dcx2]

test build r108

- Fixed the "no multi-poke data available" bug (introduced some time around Serial Poke); right-clicking on search results sometimes wouldn't load the addresses into the multi-poke address history
- When search result view mode is float, the difference column is now calculated correctly

[dcx2]

test build r109

I have an awesome new feature to introduce.  The disassembly tab now supports a call stack!  When the game is paused at a breakpoint, go to the disassembly tab and either double-click the Call Stack list box, or right-click and then click "Load". You must do this manually because the process is a little slow.

It will automatically parse the stack for the LR save word from each stack frame, and then fill the list box with the current instruction address and every bl that lead up to the current instruction.  You can double-click on any address in that list box and the disassembler will automatically jump there.

A long time ago, I wrote a guide about walking the stack.  http://wiird.l0nk.org/forum/index.php/topic,5080  It explained how to follow function calls so that you can find the best place to patch the ASM.  The new call stack list box has reduced this guide to "double-click each one of those addresses and look for something interesting"

---

- Added Nuke's SetLatencyTimer call.  Everything is much snappier now.  Auto-Update MemView goes 15 dps!  Breakpoints hit faster.
- Disassembler uses random temporary file name instead of diss.bin; prevents problems where diss.bin gets locked somehow (this should help giantpune)
- Added Disassembler Context Menu items that jump to function start and end

- When left clicking the Step Out button , it will attempt to guess whether leaf or stack frame is the appropriate method of stepping out.  In rare circumstances, it can be fooled by conditional blr's (beqlr/bnelr/etc, but not plain old blr), however all it does is go an extra step out so there's no real harm.  You can still manually choose leaf, stack frame, or walk to blr from the Step Out context menu.  Walk to blr is still useful sometimes, like when using the Log Steps checkbox.  It will never mess up, but it is the slowest.

[Panda On Smack]

awesome, thats very handy

ta dcx

[giantpune]

very handy indeed.  this version has fixed the crash i was getting with the last one about the diss.bin :) .  however, i notice the callstack in "forgotten" by simply changing tabs.  even if you dont click on anything in any other tab.  i went back to the breakpoint tab to look at something and when i came back to look at teh call stack, he has been wiped out again.   anyways, im sure its a pretty easy fix to clear it up.  and a great addition to the program.

[hetoan2]

yea if you click on the callstack box after it loaded it will also disappear :(

[dcx2]

It's been a long time coming, but now there's a new "official" build.

http://geckowii.googlecode.com/files/Gecko dNet 0.63.zip

- Call Stack is not cleared anymore when Disassembly tab gains focus
- Address text box context menu now supports adding or subtracting a hex offset
- Memory Viewer context menu also supports adding or subtracting a hex offset
- Source code is now hosted at Google Code!  http://code.google.com/p/geckowii/source/browse/

[James0x57]

Awesome. Pure awesome.
Thanks a ton, dcx2!