Author: Compynerd255
Posted: 30 Oct 2012 03:27:58 pm (GMT -5)
Here are some DCS wiki pages
Main GUI page, with TOC
The routine that opens the GUI stack
The routine that pushes a widget onto the stack
The data item for a text button
The data item for a text block (see this page to find out that the DCS text-editing routine changes the text field here)
From this, it appears evident that all of the data is contiguous in the block, with text, callbacks, and widget data as one block. The stack entries are most likely copied to free RAM, as finding a particular item in the stack is an O(n) operation.
_________________
Visit Betafreak Games: http://www.betafreak.com
Help Me Pay for College:
- Sign up for Fastweb through my referal link!
Posted: 30 Oct 2012 03:27:58 pm (GMT -5)
| AHelper wrote: |
| Work started again by picking up where I left off on the gui library. KermM, this is for you. I have a gui widget layout serialized somewhere. Currently, I have the text, callbacks, and widget data separate. Right now, I am making those into one data block which will be ready and used by an assembly-based interpreter. Can you share the layout that you use for DCS widgets? Or are these on the DCS wiki? (I am also looking for internal data storage for it as well (temp variables and such to see how you approached it)). |
Here are some DCS wiki pages
Main GUI page, with TOC
The routine that opens the GUI stack
The routine that pushes a widget onto the stack
The data item for a text button
The data item for a text block (see this page to find out that the DCS text-editing routine changes the text field here)
From this, it appears evident that all of the data is contiguous in the block, with text, callbacks, and widget data as one block. The stack entries are most likely copied to free RAM, as finding a particular item in the stack is an O(n) operation.
_________________
Visit Betafreak Games: http://www.betafreak.com
Help Me Pay for College:
- Sign up for Fastweb through my referal link!