Probably won't interest many people, but anyway, if anyone is interested, or they're doing something similar...


Urgh, went back to some more page investigation - mainly looking at the hex data.

It seems that entries seem to be sorted in pairs like this:

Here's some descriptors I found by poking around a little:

0x400	Offset to the "native:/" action relative to the "native:/" data
0x401	Unknown
0x402	Absolute offset to the image entry
0x408	Unknown
0xFFFF	Non-existant.  The value of this entry should be 0xFFFFFFFF

In xmenu, the descriptors are all 0x400, meaning that the values below them point to the "native:/" table.


As for page entries having different structures, it looks like it's based on the page ID.  This will allow me to make RCO Editor nicer for some IDs, but the main thing I'm worried about is the number of different IDs... (there's too many)  There's must a pattern among them :S


Here's a few

0x2049 (9)	First entry is 0x0111.  This is followed by 4 "action pairs".
0x2050 (19)	13 entries for item positioning (explained in first post) followed by 0x00, 2 "action pairs" then another 0x00
0x2053 (5)	0x00 followed by 2 "action pairs"
0x2058 (6)	3 "action pairs"
0x2060 (6)	Appears to be the same as 0x2058
0x2066 (16)	13 entries for item positioning followed by 0x00 then 1 "action pair"
0x2072 (4)	2 "action pairs"

Note, the numbers in brakets refers to the number of entries

(This post was last modified: 09/04/2007 04:15 AM by ZiNgA BuRgA.)