Discussion in 'General Discussion' started by yeager, Jun 19, 2010.
Are the wrapper dll and glass cannon still being maintained?
I believe so. I see SVN commits to glass cannon usually once a weekish.
When I try to compile glass cannon there are several functions that are referenced in the wrapper dll that are not there.
last time it was updated was 20100316 according to .. svn.
Are you using the wrapper dll from the innerspace/.net programs folder? That one is patched by ISXEQ2, and would be more up-to-date than any wrapper found on the SVN.
Thanks. That fixed the dll reference errors. I would have thought the SVN version was the more up to date. Guess that's what I get for thinking.
Any idea on these errors?
Error 6 The tag 'CustomBaseWindow' does not exist in XML namespace 'clr-namespace:EQ2SuiteLib;assembly=EQ2SuiteLib'. Line 1 Position 31. C:\Documents and Settings\Mark\My Documents\Visual Studio 2010\Projects\EQ2Suite\EQ2ParseBrowser\AboutWindow.xaml 1 31 EQ2ParseBrowser
Error 7 The tag 'CustomBaseWindow' does not exist in XML namespace 'clr-namespace:EQ2SuiteLib;assembly=EQ2SuiteLib'. Line 1 Position 31. C:\Documents and Settings\Mark\My Documents\Visual Studio 2010\Projects\EQ2Suite\EQ2ParseBrowser\LogSourceManagerWindow.xaml 1 31 EQ2ParseBrowser
Error 8 The tag 'CustomBaseWindow' does not exist in XML namespace 'clr-namespace:EQ2SuiteLib;assembly=EQ2SuiteLib'. Line 2 Position 2. C:\Documents and Settings\Mark\My Documents\Visual Studio 2010\Projects\EQ2Suite\EQ2ParseBrowser\MainWindow.xaml 2 2 EQ2ParseBrowser
Error 9 The tag 'CustomBaseWindow' does not exist in XML namespace 'clr-namespace:EQ2SuiteLib;assembly=EQ2SuiteLib'. Line 2 Position 2. C:\Documents and Settings\Mark\My Documents\Visual Studio 2010\Projects\EQ2Suite\EQ2ParseBrowser\ScaleInterfaceWindow.xaml 2 2 EQ2ParseBrowser
I'm not entirely sure it's been tested with Visual Studio 2010. ISXEQ2 and InnerSpace are written with 2008.
It may not matter at all; however, you might want to test with 2008 and see. As far as I know, everything is up-to-date and working.
I compile a version of this in 2010 without issue.
The developer currently isn't working on bot / EQ2 related functions as far as I know, but instead focusing on the parsing side / opportunities presented.
(The bot still works just fine, but may not have SF features (AAs) added to all / any classes, I don't recall which ones I had fed back for inclusion, if any).
You can remove / ignore anything that references xaml, as these windows are all used for the parsing part of the app.
I track the changes to the vcs, but I don't necessarily apply them, so I can't say for sure what errors you experience that I don't when building.
My current build copy has "eq2parseBrowser" and "parsertestconsole" projects marked as unavailable, ie, I r-clicked em and selected "unload", and then fixed any references / dependancies by removing the references.
You need :
I also have EQ2ParseEngine building but I don't recall it being required.
I had to get a specific wrapper DLL also, when we moved to SF release. That version has some issues, and I ended up removing (commenting out) the looting code which used stuff the dll didn't seem to be exporting properly.
I seem to be getting closer but I'm stuck on wrapper dll reference again.
Error 1 'EQ2.ISXEQ2.EQ2Event' does not contain a definition for 'LootWindowAppeared' and no extension method 'LootWindowAppeared' accepting a first argument of type 'EQ2.ISXEQ2.EQ2Event' could be found (are you missing a using directive or an assembly reference?) C:\Projects\EQ2Suite\EQ2GlassCannon\PlayerController.StaticGlobals.cs 146 16 EQ2GlassCannon
Error 2 Non-invocable member 'EQ2.ISXEQ2.LootWindow.Item' cannot be used like a method. C:\Projects\EQ2Suite\EQ2GlassCannon\PlayerController.cs 627 32 EQ2GlassCannon
I updated using the svn this morning and it deleted the dll I had started using. Fortunately I had a copy.
that should get you up and running
Thanks. Commenting out the loot code did get it going. Wish it was still there, however, even if not quite right.
As best I could tell, the functionality is no longer being exported from the wrapper DLL. It was before SF released, but not since.
The code was working fine prior to SF and has not altered.
I guess the next step for you will be understanding how to use GC Will respond as best I can as and when
What are the functions that are not exported anymore?
The wrapper was exporting the event "LootWindowAppeared", and does so no longer. As a result the code can't chain that event. A snippet example :
s_eq2event.RewardWindowAppeared += new EventHandler< etc and so on >
s_eq2event.LootWindowAppeared < etc and so on >
That's from around line 145 of EQ2Suite\EQ2GlassCannon\PlayerController.StaticGlobals.cs, the ChoiceWindow and RewardWindow appeared events are still exported fine but LootWindowAppeared is not. I went wandering thru the wrapper at some point near SF release to see if I could find a new one or a replacement and didn't have any luck at the time.
Once past that, we then hit the other problem, which I think is a wrong field type being exported. In PlayerController.cs at line 616, we have the "OnLootWindowAppeared" event handler, which used to be fine, and now errors saying we're using "ThisWindow.Item" incorrectly. ThisWindow is an instance of LootWindow. Item used to be an array of Item, as best I can tell. The code worked before and supports using this as an array of item. Now "Item" is just a single item. So I looked for a way to access multiple choices of loot in the loot window, and there is no other way. I think the exported definition has just gone goofy for some reason.
I think that those 2 changes cause the current EQ2GC codebase to compile without error. And, I know you aren't responsible for the codebase in any way, nor it's author or even a user of it for all I know, so thanks for taking a look at these. I'm in a position to compile, rebuild etc, if needed for testing, and I'm reasonably familiar with the codebase, if required.
Amadeus have you had a chance to look at this again? I know other things have kind of cropped up lately. Just wondering.
Separate names with a comma.