V2.3 to V2.4
------------
Features:
1> Change the app to use the map which is selected in UI-View32 so InfoKiosk will work with external map servers like Pmap
2> Interface is a bit more aesphetic

V2.2 to V2.3
------------
Features:
1> Infokiosk beacon text can now be changed from the default "Msg ?INFO to CALLSIGN for commands"
2> InfoKiosk minimises on start-up
3> Quick set-up button gets lat, lon and callsign from UI-View32

Bug:

V2.1 to V2.2
------------
1> Setup Feature added to disable sending of "Msg ?... to for Info"

V2.0 to V2.1
------------
1> Fixed a bug which caused numerous "Msg ?... to for Info" to be sent

V1.7 to V2.0
------------
1> Maintain Objects now has an option to edit the textural description. Without the need to delete and re-create the object
2> The INFOKIOSK object name can now be changed to what ever is desired.

V1.6 to V1.7
------------
1> Fixed a bug which caused message for multiple objects to be returned. Example
You had PETROL1 to 3 defined ?p would cause multiples of Send ?PETROL1-3 for info when the request was not addressed to the station running InfoKiosk

V1.5 to V1.6
------------
1> Multiple objects of the same type only return a generic name in reponse to ?INFO. .e.g.
PETROL1 PETROL2 PETROL3 returns just ?PETROL if the info reponse

V1.4 to V1.5
------------
1> Importing of UI-View overlays files now allows for blank lines and additional asterix lines
2> Large maps no longer results in RUNTIME ERROR 6
3> The loopback problem where a response to ?INFO resulted in a command being on one line is now fixed with the inclusion of a . at the end of the info response message


1.3 to 1.4
----------
1> InfoKiosk beacon object is now adopted through UI-View32 if owned by someone else
2> Import / Export for UI-View objects file support
3> Multiple objects of the same type now supported
Example ?PETROL can return the objects PETROL1 PETROL2 etc
4> Objects are now sorted alphabetically on start-up
