- when on global view, clamp the lat/lng so it's not beyond +-180 E/W and +-90 N/S - otherwise the server no longer returns data
- fix refresh on chat tab changing - it was firing too early on first page load
- central point for checking for 'error: "out of date"' response from server
- in 'out of date' state, an error dialog is shown and no further requests are sent to the server
- request queue has central point for request adding - now request count is accurate, not just for COMM requests
- request error count is cleared after a period of no requests failing
improvements could be made to our version handling (currently we just take their version string and assume it'll work, with no checks for changes - needs some thoughts on sensible handling)
- no GUIDs in chat for players or portal details - so remove player GUID related functions
- remove player guid code from COMM
- update portal_info functions to compare to player name rather than guid
this way, if you switch back to IITC, then quickly move/zoom (as often is done), unnecessary network requests are avoided
because of the change, there's no need for chat to have it's own resume hook - it already hooks into the refresh code and this is now triggered quickly
For both of them returning false will interupt the default action
'geoSearch' is called when something is entered in the search box.
The argument is the string entered in the search box
'nicknameClicked' is called when a nickname is cliked.
The argument is an object with 2 properties:
- 'event' contain the standard event object
- 'nickname' contain the nick of the user
- remove public @mentions from the faction chat channel
- add default case to chat text handling. if a new message fragment type is added, at least something will be shown in chat instead of being blank (as happened when AT_PLAYER was first introduced)
- highlight your own player name in the chat column in yellow for things you said/actions performed - similar to @mentions from other players
this fixes an issue that, in theory, could have occured with the public chat fetching and over 200 sequential skipped ([secure]) messages. the recent change to skip SYSTEM_NARROWCAST for faction chat was much more likely to trigger the same issue
also
- lighten the red colour used in public chat - was almost impossible to read before
- set the faction chat message count to 100 (it was 50, then bumpped to 200 briefly to work around chat issues)
