by placing a marker before your event handler like so:
void function_that_never_gets_called(void)
{
serial.string = "magic string";
event.some_property = 0;
}
event handler function()
{
...
}
A program can scan the .oex file, looking for the magic string; the
event handler will always be <n> bytes after it. The event. line
after the string will give you the event object's address.
You can repair any number of event objects by scanning the entire .oex file.
At 09:18 PM 3/23/2008, tinslwc wrote:
>Working on this issue further, I have found that you can remove the
>first two lines (setting the oEvent object class). That part is
>fine. I have also found that using a hex editor, you can manually
>insert the address into the oopic executable file (hex compiled file)
>and eliminate the oRAM object entirely. After finding the address of
>the subroutine, calculate the hex notation for the address, open the
>source code in the V6 compiler, open the .oex file in a hex editor,
>find the initial object declaration (won't be easy) and insert the
>address here (low byte first), go back to the oopic program and click
>the green arrow to send to oopic. Make sure you do not change any
>code as it will recompile and you will lose any changes that you
>made. I would recommend using the ram object over this but if you
>need to do it, it will work.
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment