Problems getting to ItemInfo (removed from WoWItem API)

[LiquidAtoR]

[SIZE=1][SIZE=2]Styx.WoWInternals.WoWObjects is not accessible because of security level[/SIZE].[/SIZE]

Whatever I do to get to ItemInfo (used to be part of WoWItem, now it's on it's own under WoWObjects) I either get a security level problem, or I can't reach it because it's non existing in other parts of WoWObjects where I do have clearance to grab back on it (Like <WOWITEM>).

Anyone any suggestions?

Styx.WoWInternals.ObjectManager.GetObjectsOfType[WoWItem]<WOWITEM<WOWITEM>

<WOWITEM><WOWITEM> doesn't contain ItemInfo anymore (beta 10 did, quest beta 1 doesn't)

Styx.WoWInternals.ObjectManager.GetObjectsOfType[WoWObjects]<WOWOBJECTS<WOWOBJECTS>

<WOWOBJECTS><WOWOBJECTS> gives security errors (here ItemInfo is underneath).

And yes, I use < > instead of [ ], but for some reason the board doesn't allow me to post the WoWItem and WoWObjects with < around em inside CODE tags (probably security measures)
Used to be Styx.WoWInternals.WoWObjects.WoWItem.ItemInfo
Now it's Styx.WoWInternals.WoWObjects.ItemInfo (and no more rights to grab on it)

 

[ski]

I was having this issue too, here is the word from MaiN:

(10:08:02 AM) MaiN: ItemInfo inf = new ItemInfo(id)
(10:08:23 AM) MaiN: Or simply
(10:08:27 AM) MaiN: WoWItem.CachedInfo
(10:08:45 AM) Me (MSN): what does cachedinfo return
(10:08:52 AM) MaiN: an ItemInfo
(10:09:10 AM) Me (MSN): any difference between creating an ItemInfo object or using cached?
(10:09:14 AM) MaiN: yes
(10:09:20 AM) MaiN: cached info is faster than creating a new one

So you should be able to do:

ItemInfo inf = someItem.CachedInfo;
<id of="" item="">
or if you do not have a valid WoWItem instance to work off (like the items in a merchant frame):
ItemInfo inf = new ItemInfo(item ID)
</id>

 

[LiquidAtoR]

Thanks, Liquid.

ps, would be nice if the API was updated along with those changes.
I realize that it's alot of work, but it would prevent this from happening at all.

 

[ski]

Thanks, Liquid.

ps, would be nice if the API was updated along with those changes.
I realize that it's alot of work, but it would prevent this from happening at all.

Just reference the objects in VS and use the object browser. Instant updated API.