Custom Query (105 matches)

From the wiki: "Only one AI remembers the location of Konoko, while the others go inactive: ​http://edt.oni2.net/mov/1remembers.wmv Also, its always the last AI that is spawned that remembers where Konoko is and attacks her."

I'm moving this here even if it isn't addressed for a while because it didn't belong where it was. My only question is whether the BINACHAR Omniscient flag and the ONCC HostileThreatDefiniteTimer field were taken into account when declaring this a bug.

When testing the AE in the upcoming OS X 10.10 Yosemite, I got the follow message in Console:

XmlTools: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number. Call location: XmlTools: 0 CarbonCore 0x00007fff94d08dc3 ___Gestalt_SystemVersion_block_invoke + 113 XmlTools: 1 libdispatch.dylib 0x00007fff9395ec13 _dispatch_client_callout + 8 XmlTools: 2 libdispatch.dylib 0x00007fff9395eb26 dispatch_once_f + 117 XmlTools: 3 CarbonCore 0x00007fff94cb14da _Gestalt_SystemVersion + 987 XmlTools: 4 CarbonCore 0x00007fff94cb10c7 Gestalt + 144 XmlTools: 5 QtCore 0x0000000100257836 _ZN9QInternal17activateCallbacksENS_8CallbackEPPv + 2582 XmlTools: 6 ??? 0x00007fff62f25ceb 0x0 + 140734853438699

I don't know why or when this is being called. Are you calling the Gestalt() function directly or is Mono doing that for you? I also don't know if this affects anything adversely because I don't know if you are actually looking at the OS version.

The program still seemed to work fine in 10.10, so I'm just filing this as a trivial bug so that you're aware of it. I suspect it's actually a Mono bug that we can't do anything about.

As seen in ​http://wiki.oni2.net/File:AEI_core_window.jpg, core "Tool" packages end up with the status __D when they ought to be I_D. Some suggestions:

1. The simplest solution is to remove the State column altogether, as there's nothing the user can do about the state of these packages anyway :-)

2. Then again, perhaps with the new checksum verification feature, it will be easier to confirm that "Tools" are installed.

3. The State column could even be slightly re-purposed so that when a change to an installed "Tool" is detected, it triggers the _U_ flag, or else, to avoid confusion, this State column can show a different flag like _M_ for locally-modified files.