Gecko dotNET release thread (version 0.65 now!)

[WiiOs-Ozelot]

ok, also i have xp sp2 :D but, or I test that again

[dcx2]

test build r77

-Fixed a devastating bug that could cause loss of codes when reconnecting!
-Fixed a bug where deleted search results might not disappear from the listview
-Added customizable BPNext address; sometimes the code handler would run multiple times in a frame, so if you can find a more reliable address now you can use that instead

It's been a while since we've had an official build, and the the vanishing code bug is a showstopper, so unless someone finds something else wrong with this in the next couple days it's going official 0.62.

[WiiOs-Ozelot]

mh i found a bug, but i dont know from what ???
the wiird.dot.net works but when i send cheat codes few seconds later game frozen




i dont know from what hmmm... when i start the normal wiird works fine.
i think a code intepretation error by reading data? :eek:

[hetoan2]

Ozelot post in the right area -.-

Bugs and requests for geckoDotNet are found here:
http://wiird.l0nk.org/forum/index.php/topic,4954.msg53005.html#new

post in the right area next time.

[dcx2]

when changing the selected code in the left pane, you want any changes in the right pane to be stored to the code.  when dragging and dropping, there was temporarily an extra item in the list, and it was changing the selected code at the wrong time so that it thought the old item's right pane was what you wanted to be stored.  A relatively simple fix that took quite some time to isolate...

So...assuming that no one else finds any other bugs...this will go 0.62 soon...honest!   ;)

test build r78

btw, since I'm already making a post...Ozelot, check to see if "Pause While Sending" is checked.  I can imagine how that might cause problems.  But don't post back here...take it to the bug/request thread in my signature.

[wiiztec]

You still haven't fixed the register display

[Panda On Smack]

He's not exactly getting paid for this so easy on the demands, maybe appreciate the HUGE advancement it's been through

[wiiztec]

Not trying to come off as demanding but it's a pretty big problem, I don't think a new official release should be made until it is fixed

[dcx2]

Cosmetic bugs that only affect the appearance of data are not nearly as catastrophic or annoying as bugs which get rid of codes.  You can still use Text View, even if it looks funny.

First and foremost is the protection of a hacker's prized possessions - the codes - and everything else is secondary to that.

The Text View shouldn't be too hard to fix, though.  Since you're such a nice guy I'll try to make sure it's adjusted before 0.62.

[dcx2]

test build r80

-Text View Breakpoint Register window no longer wraps around
-All (most?) of the popup windows should now center above the parent when they become shown

[dcx2]

Changes since 0.61; see this post http://wiird.l0nk.org/forum/index.php/topic,4886.msg46432.html#msg46432

All TextBox's that had an address are now special AddressTextBox's.  What does that mean for you?

- They check the validity of their inputs.  If the address is not valid, the background is colored a faint red.
- They prevent you from entering non-hex digits
- They support history.  All of the history functions are available from the context menu.  In addition...
-- Double-click to show history
-- up/down to scroll through history
-- Ctrl+Enter adds the address to the history
-- Ctrl+Delete removes the address from the history
-- Ctrl+Shift+X to cut all history addresses into the clipboard
-- Ctrl+Shift+C to to copy all history addresses into the clipboard
-- Ctrl+Shift+V to paste all history addresses from the clipboard
-- Ctrl+Shift+Delete to clear the history
-- Enter/Click on a history address in the dropdown to select it
-- Delete on a history address in the dropdwon to remove it
-- Auto history checkbox in context menu will add any valid address to the history when the textbox loses focus.  This is enabled by default

- All (hopefully) dialogs should pop up centered above the app
- sleep(100) after gecko.Pause() because otherwise it doesn't seem to work
- eliminated hex->float rounding
- Connecting can now be canceled
- Added customizable BPNext address; sometimes the code handler would run multiple times in a frame, so if you can find a more reliable address now you can use that instead


Search:
- Search comparison type dropdown lists all options without a scrollbar
- Loading search sets "last value" correctly
- MessageBox when there are no search results
- Poke initialized with old value
- Fixed a bug where deleted search results might not disappear from the listview


Memory Viewer:
- Just about everything that selects a new Memory Viewer address will center that selection
- Pageup/Pagedown work in the Memory Viewer address text box


Breakpoints:
- Fixed conditional branch detection bug (less than and equals were backwards)
- Register Editor Dialog comes up on top if needed, textbox is given focus when shown
- RegisterDialogBox exception fixed
- Show Mem supports lhz
- BPCondition context menu - Copy, SRR0 !=, SRR0 ==, Delete, Clear
- Delete key works in BPCondition list
- Rearranged Breakpoint Tab so that Active Conditions is resizable
- Active Conditions now has a checkbox to enable/disable conditions
- Breakpoint Condition Value register is now updated with the current selected register's value:
-- on a breakpoint
-- on a step
-- when the current selected register dropdown is changed
--- This was designed primarily to make SRR0 != conditions easier to set (i.e. "don't break on this instruction").  But it should make all conditions easier.
- Breakpoint Group Conditions
-- all conditions in a group are ANDed, but all groups are ORed.  Only one group needs to be true, but all conditions in that group must be true
-- Breakpoint group number is prefixed to the condition in the ListBox
-- To change condition group number, select conditions to change, right click, Set Condition Group, enter the new value and press enter
- Copy All breakpoint conditions, and a separate Copy for just the current condition
- Paste copied conditions into the list
- Step Until; will repeatedly Step Into until the Breakpoint Conditions are met.  Can be canceled


Disassembly:
- Disassembly context menu can now Copy all of the disassembly to the clipboard
- Disassemble() properly closes FileStream
- Enter key in one-line assembler emulates clicking Assemble
- Fixed one-line assembler problem with bctr/bctrl/blr


GCT Codes:
- Fixed bug where reconnecting could cause codes to be lost
- Fixed bug where drag/drop could cause codes to be lost
- Generate the cheat stream like WiiRDGUI does; appears to have fixed some Send Cheats bugs...?


Watch List:
- Watch list updates faster.  Still slower than Memory Viewer, but should be more tolerable now
- Fixed Watch list random exceptions

[dcx2]

test build r82

- Breakpoint Register Edit View will show float registers as floats.  Text View still shows their hex values
- Adding Breakpoint Step logging
-- Click on the checkbox to specify the file to save the log to
-- On a breakpoint or a step, the address and its instruction are written to the log file
-- In addition, the values for each register used in the instruction will be appended to the end of the string
-- Specifying a pre-existing file will append new values to the end, so you don't have to worry about over-writing and losing your log
-- The log is flushed after each instruction is written, so you can read it while it's being written to
-- To clear the log, first uncheck "Log Steps" to close the log, then you can delete all the text and save, or just delete the file

[Romaap]

Breakpoint Step logging! :O
*claps hands in joy*

[James0x57]

That breakpoint logging is frikin epic mate! Thank you!

[dcx2]

test build r83

- All AddressTextBox should REALLY be autohistory by default.  Honest.  For real this time!

- bl/blr will indent the log to help highlight function calls.  set breakpoint will remove all indenting
- instructions are padded so that the detailed log information is always lined up nicely in Windows Notepad
- properly detects float registers when logging (before, a branch like b 0x800f060 would have confused it by making it look for float register 060)
- for load/store, the address is written to the log, as well as a peek of the current value at that address
- Conditional branches now add a row of "..." when they are taken, to highlight the changing instruction's address

The logging feature is very useful with Step Until SRR0 == X.  Start at the instruction you want, pick the ending instruction X, and when you press Step until it will repeatedly go through and record just about everything for you.