Talk:RCOXML Objects: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
Line 76: Line 76:
| colspan="7" |  
| colspan="7" |  
|-
|-
| paf::Ph'''XmBar'''::WidgetType(void) || {{cellcolors|#aa0000}} <abbr title="the unnofficial name doesn't matches with the official name">'''XMenu'''</abbr> ? ||  
| paf::Ph'''XmBar'''::WidgetType(void) || {{cellcolors|#aa0000}} <abbr title="the unnofficial name doesn't matches with the official name">'''XMenu'''</abbr> || <XMenu xmenuOnScrollIn="event:native:/Bar::onScrollIn" />
|-
|-
| paf::Ph'''XmItem'''::WidgetType(void) || {{cellcolors|#aa0000}} '''XMList''' ? ||  
| paf::Ph'''XmItem'''::WidgetType(void) || {{cellcolors|#aa0000}} '''XMList''' ? ||  
|-
|-
| paf::Ph'''XmList'''::WidgetType(void) || {{cellcolors|#aa0000}} '''XList''' ? || <XList xlistOnScrollIn="event:native:/XmbMenu::OnScrollInXmList" /><br><XList xlistOnFocusRight="event:native:/OnFocusRightContentListFirstListPage" />
| paf::Ph'''XmList'''::WidgetType(void) || {{cellcolors|#aa0000}} '''XList''' ? || <XList xlistOnScrollIn="event:native:/XmbMenu::OnScrollInXmList" />
|-{{cellcolors|lightgrey}}
|-{{cellcolors|lightgrey}}
| colspan="7" |  
| colspan="7" |  

Revision as of 16:58, 30 April 2018

Rcomage unknown object attributes

At the time of documenting the RCO format for wiki it was posible to identify some/lot of unknown attributes, in the link there are a few of them listed as dirty notes (later was identifyed some more that are not included in the link). At this point there is no need for that dirty notes because the new names of the identifyed attributes was used in the tables in wiki, the dirty notes are just kept to have a record of the changes, and liked here because are very related with this page

Menu lists and menu items

Type Name Displayed as Notes
Suggested names
for Wiki		 In rcomage In official RCOXML code In official VSH Exports
0x804 XmBar ? XMenu name="xmenu" XmBar XMB Main Menu, horizontal list placeholder Main XMB
0x805 XmItem ? XMList name="list_sysconf" XmItem ? XMB Main Menu, horizontal list item
0x806 XmList ? XList name="xlist_video_config" XmList ? XMB Main Menu, vertical list placeholder
0x809 MenuList MList name="mlist_select_update_method" MenuList Context Menu, vertical list placeholder Menu when pressing triangle
at right side of the screen
0x80A MenuItem MItem name="mitem_select_network" Context Menu, vertical list item
0x80B UnknownList ? ObjUnknown0xB 0x80B is the "List"
0x80C is the "Item"
0x80C UnknownItem ? XItem name="item_xlist_video_config_volume"
0x813 List LList name="list_edit_apcnf7" List Editable Menu, horizontal list placeholder Like in network settings
0x814 Item LItem name="litem_edit_apcnf7_0" Editable Menu, horizontal list item
0x817 InfoList IList name="ilist_ms_info" InfoList Information Menu, vertical list placeholder Like in audio file info
0x818 InfoItem IItem name="item_ms_info_size" Information Menu, vertical list item
0x81C CheckBoxList CheckboxGroup name="checkbox_list_npsignin" CheckBoxList Checkbox Menu, horizontal list placeholder Like in poweroff screen
0x81D CheckBoxItem CheckboxItem name="checkbox_item_select_auto_power_off" CheckBox ? Checkbox Menu, horizontal list item
  • Problematic names and values are marked in red
  • The "Items" doesnt have standard attributes, only have 3 specific attributes, and that atributes uses to be a reference (ref/text/image but not always, there are some expections). This is an easy way to identify them
  • The "Lists" does have standard attributes, and a variable number of specific attributes based on its purpose, some of them matches partially with other "list" objects
  • If the previous sentence is true, it means we know the first 21 attributes of ObjUnknown0xB (the standard ones, shared by a lot of objects, always located in the same positions) http://www.psdevwiki.com/ps3/Template:RCO_TOC_Objects_standard_attributes and the specific ones can be found by getting inspiration in the specific attributes of the other "list" objects and the test-error method (first one uses to be a "counter" of childrens, then a variable number of "stuff", and at the end a bunch of "events")

WidgetType

See the "paf" VSH Exports

It seems the Widget is an identifyer of what rcomage and this wiki page baptished unnofficially as "objects", of all them or only a group

By looking at the internal RCO structure is obvious that the value used internally to identify every "object" is the first field of what we has been naming Template:RCO TOC entry common area, or in other words, the Template:RCO TOC entry types

So the question is... all "RCO TOC entry types" should be considered WidgetType ? (and consequentlly needed to be renamed in wiki pages)... or only a group of them are considered "widgets" ? and there is other group (no idea wich one by now, but RCOXML Animations could have a different name)

By looking at this list is posible to make a list of the exports that uses the keyword "WidgetType" and deduce the correspondency with the names we have been using in rcomage/wiki. Some of the "unnofficial" names we have been using matches exactlly, others partially, and there are a few "new" names hard to deduce to wich "object" corresponds, and probably are included the 2 infamous ObjUnknown0xB and ObjUnknown0x1B that are completlly unknown for rcomage and doesnt seems to be used in any of the official PSP and PS3 firmwares

VSH Exports string chunk name in RCOmage Notes
paf::PhScene::WidgetType(void) Page ?
paf::PhPlane::WidgetType(void) Plane
PlaneDiv ? Group ?
paf::PhXmBar::WidgetType(void) XMenu <XMenu xmenuOnScrollIn="event:native:/Bar::onScrollIn" />
paf::PhXmItem::WidgetType(void) XMList ?
paf::PhXmList::WidgetType(void) XList ? <XList xlistOnScrollIn="event:native:/XmbMenu::OnScrollInXmList" />
paf::PhMenuList::WidgetType(void) MList
paf::PhList::WidgetType(void) LList
paf::PhInfoList::WidgetType(void) IList
paf::PhCheckBoxList::WidgetType(void) CheckBoxGroup
paf::PhCheckBox::WidgetType(void) CheckBoxItem
paf::PhProgress::WidgetType(void) Progress
paf::PhScroll::WidgetType(void) Scroll
paf::PhText::WidgetType(void) Text
paf::PhLabelText::WidgetType(void) EditBox ? The object named "EditBox" by rcomage is exactly like the object "Text" with some attributes added at the end
paf::PhItemSpin::WidgetType(void) ItemSpin
paf::PhNumSpin::WidgetType(void) Spin
paf::PhButton::WidgetType(void) Button
paf::PhClock::WidgetType(void) Clock
paf::PhLevelMeter::WidgetType(void) Meter
paf::PhIPAddr::WidgetType(void) Edit All the "event" strings found in PS3 for this object contains the name "ipaddr" !
paf::PhLabelPrim::WidgetType(void) ?
paf::PhWidget::WidgetType(void) ? weird, a WidgetType named Widget ?... this sounds too generic, maybe is the name of the "ObjectTree"
  • Other unnofficial "object" names that are not in the table:
    • General
      • type=0x00 ObjectTree
    • Items
      • type=0x0C XItem
      • type=0x0A MItem
      • type=0x14 LItem
      • type=0x18 IItem
    • Others
      • type=0x19 Icon
      • type=0x10 Action
      • type=0x1A UButton
      • type=0x0E ModelObject
    • Unknowns
      • type=0x0B ObjUnknown0xB
      • type=0x1B ObjUnknown0x1B

Some texture using object and attribute names

The names of this images indicates the attribute names of some RCOXML objects. Are the object attributes with datatype/reftype "image" 

<Image name="tex_default_text_field" src="Images\tex_default_text_field.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_text_focus" src="Images\tex_default_text_focus.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_text_field_focus" src="Images\tex_default_text_field_focus.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_progress_base" src="Images\tex_default_progress_base.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_progress_base_shadow" src="Images\tex_default_progress_base_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_progress_slider" src="Images\tex_default_progress_slider.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_base" src="Images\tex_default_scroll_base.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_base_shadow" src="Images\tex_default_scroll_base_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_slider" src="Images\tex_default_scroll_slider.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_arrow_up" src="Images\tex_default_scroll_arrow_up.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_arrow_up_shadow" src="Images\tex_default_scroll_arrow_up_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_arrow_down" src="Images\tex_default_scroll_arrow_down.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_scroll_arrow_down_shadow" src="Images\tex_default_scroll_arrow_down_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_spin_arrow_up" src="Images\tex_default_spin_arrow_up.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_spin_arrow_up_shadow" src="Images\tex_default_spin_arrow_up_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_spin_arrow_down" src="Images\tex_default_spin_arrow_down.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_spin_arrow_down_shadow" src="Images\tex_default_spin_arrow_down_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_check" src="Images\tex_default_check.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_check_shadow" src="Images\tex_default_check_shadow.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_lvmeter_on" src="Images\tex_default_lvmeter_on.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_lvmeter_off" src="Images\tex_default_lvmeter_off.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_lvmeter_focus" src="Images\tex_default_lvmeter_focus.png" format="gim" compression="zlib" unknownByte="0" />
<Image name="tex_default_lvmeter_bg" src="Images\tex_default_lvmeter_bg.png" format="gim" compression="zlib" unknownByte="0" />

ObjUnknown0xB

*Superbrainstorming based on smoke. This brainstorming seems to be wrong, because the object named "XMList" by rcomage seems to be an "item" so it cant have other xml "item" childrens **what about this ?, matches prety fine with how are grouped. Main menu separated because is an special object created specifically for top XMB menu, and the others grouped in pairs for "list" and "item". Also matches how are ordered in rcomage. All this attributes appears consecutivelly in groups of two, at top... XMList and XList... then MList MItem... then ObjUnknown0xB and XItem... then LList and LItem... then IList and IItem. Note how XMList doesnt seems to have an XMItem 

XMenu

XMList
ObjUnknown0xB <------ is XMItem ?

XList
XItem

MList
MItem

LList
LItem

IList
IItem

If this is true and ObjUnknown0xB is actually XMItem it seems is posible to deduce the attributes because the other "item" objects uses pretty similar attributes (usually 3 attributes, either images or texts), to verify it are needed some/lot of tests by copying the attributes from the other items and creating a 100% custom object for the experiment also a good understanding of all the other rcoxml code, so is hard to know, im not skilled/brave to build this frankenstein but i think the theory is good enought--Sandungas (talk) 08:16, 8 December 2015 (UTC)

Objects using overrides in the "specific" attributes

The "standard" attributes contains 6 overrides and most objects uses the "standard" attributes, but additionally to this ones some of the objects (seems to) use more overrides in the "specific" attributes

  • Some menu builders
    • MList (3 ?)
    • LList (2 ?)
    • IList (1 ?)
  • Text based objects
    • Text (3 ?)
    • EditBox (3 ?)
  • Others
    • CheckboxGroup (1 ?)
    • Meter (1 ?)

anchorMode

Rcomage has some problems with this attribute from PS3 RCOs, it manages the value as 4 bytes length but in the internal RCO file structure is divided in 2 chunks of 2 bytes each. The anchor mode is specifyed by the first byte of the second chunk, is unknown why sony "reserved" 2 bytes for the first chunk (first chunk is always filled with zeroes). All this is a bit confusing and what im saying could not be completly accurate because the different endianess in between PSP and PS3 and what RCOmage does internally. RCOmage allows to choose a "data type" for every attribute by editing the file objectattribdef-ps3.ini. There is no way to extract the value accuratelly so the alternatives are to set it as "int", or you can set it to "unk" instead, this way it will be managed as raw data (no conversion applyed so you can see the real value when the info is extracted to XML)

  • Examples:
    • Extracted as "int"
      • anchorMode="0x320000"
    • Extracted as "unk"
      • anchorMode="0x3200"

Links, notes, etc...

Suggestions

Retrieved from "http://www.psdevwiki.com/ps3/index.php?title=Talk:RCOXML_Objects&oldid=49318"