I'm seeing Slot=0 for items wearing. Anyone else seeing this?

I use obj.Values(LongValueKey.EquippedSlots) > 0 for equipped items, and if (e.Changed.Values(LongValueKey.Slot) == -1) for wielded items (could be wielded by anyone).

Both lines are working as intended in the beta version of decal.

Container and slots both have broken logic in the old Decal. The changes for a call to Values(slots key, default) are as follows:


Actual value ||| Old returned value ||| New returned value

------------ ||| ------------------ ||| ------------------

-1 (no slot) ||| -1 ||| default or -1 if no default

0 (first slot) ||| default or 0 ||| 0

other ||| other ||| other


As you can see, internally -1 is used for 'no slot', such as when an item is being wielded. It is natural that default should be returned when an item has no slot, not when it occupies the first slot.


Container has also been changed, but this change shouldn't be as noticeable. In old Decal, container would be an incorrect value anytime the (unordered) packets for set container and set equipped got swapped. This was a somewhat rare case but usually caused objects in your inventory to appear to have container 0. This has been fixed.

 

-----signature-----

Something else I should point out: for those of you who got rid of Decal views with my patched inject.dll, if you are running 2961 you should not replace the inject.dll. Instead, there is a checkbox under options in Decal to disable Decal views.

 

-----signature-----

Not sure if it is a Decal issue, WIndows issue or Plugin issue but is there anyway to incorporate a method of moving and adjusting the order of plugins without having to go to the registry or use the Decal Plugin order tool that was developed a while ago (which also doesnt have a 64bit version boo :-) )


PS Is it also possible to incporpate the Decal Skins I made into the install and apply them from a dropdown if possible?

http://acheaven.buwahaha.com/DecalSkins.htm


Cheers

Suca

 

-----signature-----

I'll be honest, I want nothing to do with any further View-related changes.

I personally consider Virindi Views a valid replacement for Decal Views and the code for the Decal View system is a level of hideous that is hard to describe. Unfortunately, there is no good way to map Decal Views over to Virindi Views because VViews are entirely a managed component and Decal Views are legacy COM.

All my future plugins will be VVS only, and I think this is the best way to go. I did add an option to suppress all native Decal View rendering so there's no longer any need for Virindi's inject dll replacement.

I'm sure this will disappoint some of you but I suggest asking your favorite plugin authors to switch to Virindi Views.


Edit: It's actually faster to recode most plugins in .NET as compared to update older plugins that use COM. Plugins that are already Adapter plugins should be pretty simple to move over to Virindi Views, V has some compat code in her public repository.

 

-----signature-----

Thats all fine and dandy, but there is little info on how to implement VViews.

For example, from the wiki:
http://www.virindi.net:8080/wiki/index.php/Virindi_Views

I found the repository here:
http://www.virindi.net/repos/virindi_public/trunk/ViewServiceConnector/

After downloading the dir, file by file (which takes a while, why not .zip?), I checked out the example.

Using Visual Studio 2010, I converted the exiting example.
I added these references to my project:
System.Drawing
System.XML
VirindiViewService

In project properties, I added the compilation symbol: VVS_REFERENCED

I added the following files to my project:
ViewSystemSelector.cs
Wrapper.cs
Wrapper_Decal.cs
Wrapper_MyHuds.cs

I added the MainView.cs found in the example folder.

Then, I built the ViewWrapperCodeGenerator solution and used that to convert my existing XML to the C# source needed to insert into MainView.cs (Don't forget to modify the namespace in MainView.cs to yours.

In my PluginCore.cs, above Start() I added:
internal static Decal.Adapter.Wrappers.PluginHost MyHost;

In Startup() I added:
MyHost = Host;
MainView.ViewInit();

In Shutdown() I added:
MainView.ViewDestroy();
MyHost = null;

I build it, and still get the following warning:
Warning 1 #warning: 'DECAL_INTEROP not defined, MetaViewWrappers.DecalControls.Control.LayoutPosition will not be available.'
Wrapper_Decal.cs 289 10

My plugin does show up in VViews though, which is nice. But it also shows up in Decal tab as well. When VTank is in VViews, it does not show up in the Decal bar?

Also, I then realize that I need to remap all my GUI varables in my plugin to my src for my plugin to update the VView GUI as well.

That's where I'm at now, hope this helps someone else get started.

Ugh!! It is a SVN repository! All you need to do is download an SVN client (such as tortoise svn) and tell it to check out the URL, and it will give you a nice copy of the directory structure and everything on your system.


As for converting from an adapter decal view plugin...


If your code is adapter attribute-based, you need to change all your attributes to the vvs wrapper attributes. For instance, change [ControlReference] to [MVControlReference]. At your plugin's startup, call MVWireupHelper.WireupStart(this, Host); and at shutdown call MVWireupHelper.WireupEnd(this);.

 

-----signature-----

Ok, without trying that yet... I'm thinking doing that will disable/break the decal view, even if VViews is disabled? I'll try it and find out.

From how I understand VViews works, we can develop our programs to support VViews and Decal views simulatenously.? I'm not sure why you would even do this, but it stems into my next questions I guess.

From seeing VTank in operation, we can develop our plugin to use VView if VView is enabled, or fall back to Decal view if VView is not enabled.

If we make our plugins VView compatable, the clients will need to have VViews installed (even if disabled in decal).

If you use only my metaviewwrapper classes, your plugin will run in VVS when it is running and in Decal when it is not. VVS doesn't even have to be installed on the system.

 

-----signature-----