Unload loot to Freight Container still not work
Sorry in what version ? In the last version ?
I test yesterday the latest build, and in moment when questor open item hangar doesn't open anything
Yeah i have just test it and i can confirm it don't work.
And first with the old version i was able to fix it, now i'm unable to fix it with the last version so we need wait ise fix it.
hrm... I tested it as working fine before I merged in some corp hangar changes from bbday. I'll take another look tonight.
I have test it again now and it don't open nothing. It get stucked in that point.
And i'm sure my xml is perfect becouse i'm using it with the old version where it was warking.
06:07:51 [AgentInteraction] Attempting to close Agent Window
06:07:53 [AgentInteraction] Done
06:07:54 [CombatMissionsBehavior] UnloadLoot: Begin
06:07:55 [Cache.OpenAmmoHangar] Opening Item Hangar: waiting [4sec]
06:08:00 [UnloadLoot] Moving Ammo to AmmoHangar [('InventorySecondary_StationItems', 60004027)]
06:08:00 [UnloadLoot] Waiting for items to move to AmmoHangar
06:08:03 [Cache.StackAmmoHangar] Stacking Item Hangar: waiting [3sec]
06:08:04 [UnloadLoot.AmmoHangarStacking] Done stacking AmmoHangar
06:08:05 [Cleanup] CloseInventoryWindows: Closing other Inventory Window named [
06:08:07 [Cleanup] CloseInventoryWindows: Closing other Inventory Window named [ ('InventorySecondary_StationItems',
06:08:09 [UnloadLoot] Opening Cargohold of active ship: waiting [4sec]
06:08:13 [Cache.OpenLItemsHangar] Opening Item Hangar: waiting [4sec]
06:08:17 [UnloadLoot] Loot was worth an estimated [63.967] isk in buy-orders
06:08:56 [Questor] Wallet Balance Has Not Changed in [ 2 ] minutes.
Confirm, for me the same
Any news on that bug ?
Please, i don't want stress, but is possible fix it ? Are months we ask that.
the issue is (seemingly) the cache.cs function:
public bool OpenAndSelectInvItem(string module, long ID)
which is used for both the freight container selection and corp hangar selection in the tree on the left of the inventory window.
long ammoHangarID = Cache.Instance.DirectEve.GetCorpHangarId(Settings.Instance.AmmoHangar) - 1;
long lootHangarID = Cache.Instance.DirectEve.GetCorpHangarId(Settings.Instance.LootHangar) - 1;
have never made sense to me. Why does directeve return a value that we have to subtract 1 from before we can pass it back to directeve to select the right tree item?
I didnt write the corp hangar tree selection functions and they dont make logical sence to me so fixing it will have to be handled by someone that can make heads or tails of it.
I have fully merged in the files bbday linked to me with no changes in behavior. With the above " -1" nonsence I have to wonder if he has it working locally and only locally... like the hangarIDs arent correct for anyone except him. I really dont know.
It was mentioned by Gannondorf that we might be able to use the hangarName instead of the hangarID but I couldnt work out how to list the hangarNames. There is a directeve function to list the hangarIDs but not an equivalent to list the hangarNames. If their is a way to do this with hangar names instead of IDs I am all ears.
bbday have said me DE is unable to open 2 windows same time, so we need first close 1 windows and after ask DE open another. He have said me is that the error in your version. But i dont' know how to fix it.
I really want use your version but with that don't working i can't becouse i use GFC.
If it work i can help a lot in fixing and find bugs. A lot more than now.
i had fixed in my version.. tomorrow if i finding time i'll fork from isee version and i'll fix a lot of stuff.. and add new functions, new program qstatistic.
bbday any news ? Have you try fix the actual ise version ?
ok, I spent waaaaaay too much time on this:
I have it working great on a few toons and not working at all on another, but I think that may be limited to that corp having "odd / broken" corp hangars. This needs more testing before we'll really know if its fixed or if we have something else going on that needs attention.
FYI the comments a month ago were written while testing from the toon that is STILL failing for me, but the other toons in diff corps are working fine so I dunno.
It is working perfect now. Running the last version for some hours and seems all perfect.
You can close that issue.
Are you testing LootContainer, AmmoHangar or LootHangar?
I'd like to resolve all of them for this issue to be properly closed.
I think the last of the issues revolves about the AmmoHangar and LootHangar but not sure exactly what trips them up as it seems sporatic
ok, this is now resolved, AmmoHangar, LootHangar, LootContainer, DroneBay, etc no longer require that a window be open thus simplifying everything by a few steps and making the process MUCH less error prone.