relatively simple. The compiler is not filling in the address for the
subroutine that should run when the event is triggered. This means
that when your oWire object copies the event value to the oEvent object
operate property, it has no idea what to do. The objective of the oRAM
object is to inject the correct address into the ram space occupied by
the oEvent object. This means that you have to look through the
compiled code to get this location and if you add or change any part of
your program that comes before the event code, the address may change
(even adding the oRAM object/write commands). If you have any specific
questions about the workaround, I would be glad to assist you.
--- In oopic@yahoogroups.com, "wisequack42" <wisequack42@...> wrote:
>
> Hmm, I guess I should actually read something before jumping in, eh?
>
> Does this: http://tech.groups.yahoo.com/group/oopic/message/37874
> address this problem? I'm not entirely sure I follow what's going on,
> but I can take another crack at deciphering it after finishing the
> program, I guess.
>
------------------------------------
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