13/03/2007, 06:18 AM
13/03/2007, 01:46 PM
always thought that the battery icon blinks to slow when recharging? ;P
system_plugin_fg.rco
Anim Data » anim_battery_charging » 0x907 » value in miliseconds(?)
see it in action :
Source: YouTube
system_plugin_fg.rco
Anim Data » anim_battery_charging » 0x907 » value in miliseconds(?)
see it in action :
Source: YouTube
13/03/2007, 01:48 PM
Nice finds as always!
I should have guessed....
Man I wish I didn't have so many tests so I could help figure out all this stuff! :(
I should have guessed....
Man I wish I didn't have so many tests so I could help figure out all this stuff! :(
23/03/2007, 11:40 PM
Hehe, just downgraded to 3.03 OE-C so I can play around with this too :)
Well, I found out what the values 4-7 are - they're strengths of the individual channels.
Doesn't seem to affect topmenu's xmenu though. I tested it with the loading circle image.
Valid values are from 0 to 1, so 0.5 means "half" strength. By default, it's always 1, meaning nothing's changed.
4 - Strength of Red Channel
5 - Strength of Green Channel
6 - Strength of Blue Channel
7 - Strength of Alpha Channel
Also, with the hex values, it seems that it will always start at item 14 (that is, item 14 is the first hex value).
It seems to contain all sorts of weird values Though as for xmenu, it contains pointers to the "native" table:
16 - "native:/OnXmbInit"
19 - "native:/OnXmbPush"
21 - "native:/OnXmbContextMenu"
23 - "native:/OnXmbCursorMove"
25 - "native:/OnXmbScrollIn"
Well, I found out what the values 4-7 are - they're strengths of the individual channels.
Doesn't seem to affect topmenu's xmenu though. I tested it with the loading circle image.
Valid values are from 0 to 1, so 0.5 means "half" strength. By default, it's always 1, meaning nothing's changed.
4 - Strength of Red Channel
5 - Strength of Green Channel
6 - Strength of Blue Channel
7 - Strength of Alpha Channel
Also, with the hex values, it seems that it will always start at item 14 (that is, item 14 is the first hex value).
It seems to contain all sorts of weird values Though as for xmenu, it contains pointers to the "native" table:
16 - "native:/OnXmbInit"
19 - "native:/OnXmbPush"
21 - "native:/OnXmbContextMenu"
23 - "native:/OnXmbCursorMove"
25 - "native:/OnXmbScrollIn"
24/03/2007, 04:53 AM
ZiNgA BuRgA Wrote:Hehe, just downgraded to 3.03 OE-C so I can play around with this too :)
Well, I found out what the values 4-7 are - they're strengths of the individual channels.
Doesn't seem to affect topmenu's xmenu though. I tested it with the loading circle image.
Valid values are from 0 to 1, so 0.5 means "half" strength. By default, it's always 1, meaning nothing's changed.
4 - Strength of Red Channel
5 - Strength of Green Channel
6 - Strength of Blue Channel
7 - Strength of Alpha Channel
Also, with the hex values, it seems that it will always start at item 14 (that is, item 14 is the first hex value).
It seems to contain all sorts of weird values Though as for xmenu, it contains pointers to the "native" table:
16 - "native:/OnXmbInit"
19 - "native:/OnXmbPush"
21 - "native:/OnXmbContextMenu"
23 - "native:/OnXmbCursorMove"
25 - "native:/OnXmbScrollIn"
great the man himself ;P
any clue why the xmb pushs back to default on OnXmbPush?
EDIT by ZiNgA BuRgA: vshmain.prx discussion can be found here
24/03/2007, 05:09 AM
good question iwas wondering the same thing
ive been looking for a page data with the defaults but can't seam to find the right one :(
ive been looking for a page data with the defaults but can't seam to find the right one :(
09/04/2007, 04:13 AM
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:
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
Note, the numbers in brakets refers to the number of entries
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:
Descriptor
Value
Value
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" |
09/06/2007, 03:05 AM
09/06/2007, 04:53 AM
they really do look good man, nice 1! i wish i new about all that technical shiznit!
09/06/2007, 06:48 AM
''anime data'' aren't to RCO edit v1.14d ?