Bernardo Reis (1096507) I'm trying to remove the procedure number and letter part. This is how the label setting is: Label=GND:DEP:1:CALLSIGN,0,0:SID,8,0,3,10 However this is what I get: My goal would be to show just OLB or ORV
Juha Holopainen (839337) @Bernardo Reis (1096507) Try "13" instead of "3,10". The syntax allows either no ExtraData field or one field that contains the sum of the selected option values.
Tommaso Dalla Spada (1614361) With the latest beta the GS item in the labels seems to not work with our setup. Label=GND:DEP:0:ALRT,0,0:ASSR_E,0,1:COMM,0,1 Label=GND:DEP:1:CALLSIGN,0,0:WTC,0,1:DRWY,0,1 Label=GND:DEP:2:ATYP,0,1:GS,0,1 Label=GND:DEP:3:STS,0,0:RMK,0,1
Juha Holopainen (839337) @Tommaso Dalla Spada (1614361) Yes, sorry about that. One line of old redundant code caused the field to clear itself. As it was only a matter of removing that one line, I've compiled the plugin again with that fixed, just download the file again.
Mark-Julius Pikat (1051954) Bug 1: When loading the ground layout, I have LVP maps automatically enabled. Bug 2: In addition, maps causes following errors: [22:00:00] File GRpluginMaps.txt contains bad information: Line 910 : SYMBOL:HLS:N059.22.14.300:E024.33.14.898 // Alliku (Problem: Invalid longitude coordinate) // commenting slash at the end of the coordinate doesn't work anymore, and when removing those, I am getting another error: [22:01:45] File GRpluginMaps.txt contains bad information: Line 10272 : LINE:N059.25.04.556:E024.47.59.958:N059.25.04.634:E024.47.60.000 (Problem: Invalid line end position) (in previous versions those "60.000"-ending coordinates were drawing correctly)
Juha Holopainen (839337) (1) The LVP maps is probably an initialization order issue of some sort, as the correct maps appear at the next full minute when the map activation is automatically refreshed. I'll look into it. (2) Comments are supported only as their own lines. The function used by the code to read the last data field of a line may in some cases end up disregarding the comment text and thus provide the intended result, but it's a coincidence rather than design. It's always best to stick to the line syntax exactly as it is in the documentation - even if something else happens to work at one point, it may stop working later on. The same goes for invalid coordinate values - 60 seconds is not valid and instead of assuming the user meant the next full minute, the parser by design flags it as an error and forces the user to provide valid data.
Marius Linge (1621930) I'm unable to get GS working in labels with the following configuration. It seems that the label has allocated space for it, but no value is appearing. Label=GND:DEP:2:ATYP,0,0:WTC,0,2:GS,0,3:RMK,0,4 Label_GS=1,1,1,1
Juha Holopainen (839337) Marius Linge (1621930) I'm unable to get GS working in labels with the following configuration. It seems that the label has allocated space for it, but no value is appearing. The space before the RMK field looks about 4 whitespace characters wide as requested in your definition. Assuming you've read this thread before posting and downloaded the updated file, I'm not sure what the issue with the GS field would be as it seems to be working for me. @Hongye Rudi Zhang (1326158) The coordinate issue is a typo in the code. All the other formats should work fine but as changing all the coordinates in your files is probably not an option, you'll have to wait for the next update. Your Window_APP setting doesn't match with any of the possible options. You were likely going for the 6 parameter version <index>,<state>,<x>,<y>,<w>,<h> and are missing either the index or state parameter. @Sergej Singer (1407054) The code does currently work on the assumption that there are no duplicate "folder\name" entries and that it's therefore safe to stop looking after the first match is found. With airport-based filtering of the maps list, having duplicate entries in the data file is acceptable and I agree that the handling of them could be improved. Possibly the code could just look for the first map that would actually be drawn instead of the first in the data file - or just activate all matching ones. I'll evaluate the possible options.
Hongye Rudi Zhang (1326158) I got this error [19:00:51] File GRpluginMaps.txt contains bad information: Line 32 : COORD:N040.03.50.018:E116.36.41.223 (Problem: Invalid longitude coordinate) [19:00:51] File GRpluginStands.txt contains bad information: Line 3 : STAND:ZBAA:A106:N040.04.55.200:E116.35.00.600:25 (Problem: Invalid longitude coordinate) also [18:55:03] File GRpluginSettings.txt or GRpluginSettingsLocal.txt contains invalid data for item Window_APP (1,2160,1010,400,300)
Sergej Singer (1407054) Hi, I'm not sure if it should be considered feature or bug, but I have a problem. Let's say, I have 10 airport layouts and in every each of them there's a map for displaying Taxiway Labels. Every map is located in a folder "Labels" and called "Taxiways", so the path to every each of them is going to be Labels\Taxiways. As I found out, if you try to reference this map for a shortcut or for a OTHER_MAP_ACT, GRP will pick only the ever first defined map and ignore the rest 9, just like in TopSky. That's an issue. Of course the simplest solution would be to name every map differently, but that would eliminate the purpose to have simple names instead something like Label\EDDF Taxiways and so on. Would it be possible to make GRP (and TopSky as well in that matter) to pick up all the maps with the same name and turn them on, or make paths more specific like EDDF\Labels\Taxiways?
