I have completed Version 3 (The Final Version) of the GPS Waypoint Route Editor.This version now has the following additional features: - Extended to accommodate up to 40 waypoints - Ability to insert a waypoint anywhere in the list (not just at the end). - Ability to delete a waypoint anywhere in the list. - Ability to move Waypoints Up or Down the list. - Scroll bars so that you can get to all of your waypoints!!(previous version only fitted 1028x768 screens or higher). - Ability to designate your waypoints as Airfield, Intersection, VOR or NDB.As this is going to be the final version I want it to go out error/bug free and to incorporate all the functionality that Simmers might need.View a screenshot here:http://forums.avsim.net/user_files/151710.jpgIf you would like to receive a copy for testing and evaluation please e-mail me: [email protected]

Hi Jim,I think the best way to get more feedbacks is to release it as a public beta. It's freeware, anyway. At least it will save you from sending it to any mail you receive, and may be a lot of them. Let the people download it, try it and report bugs and functionality requests through this forum. It's just MHO.Best Regards,GigP.S. By the way I downloaded your previous version and when I try to open a .pln file, an error "No file opened" shows up. I tried with different plans and the same thing happens.

>Hi Jim,>>I think the best way to get more feedbacks is to release it as>a public beta. It's freeware, anyway. At least it will save>you from sending it to any mail you receive, and may be a lot>of them. Let the people download it, try it and report bugs>and functionality requests through this forum. It's just MHO.>>Best Regards,>>Gig>>P.S. By the way I downloaded your previous version and when I>try to open a .pln file, an error "No file opened" shows up. I>tried with different plans and the same thing happens.Gig,I've put out 2 releases as public betas and had quite a lot of feedback on which to base Ver3. I think Ver3 is ready but just want to be sure, its very hard to spot your own mistakes!!Other people have e-mailed me with the same "No File Opened" problem. It has usually been because the PLN file was either created (or edited) by another Add-On, which alters the file structure slightly or because the PLN has more than 25 waypoints.If you open the PLN file using Flight Planner within MS2004, edit it slightly, then re-save. This will restructure the PLN file and then my Route Editor will be able to open it (Provided its less than 25 waypoints). Version 3 will allow 40 waypoints.If people want more than 40 - now's your chance to ask for it!RegardsJim

>Gig,>>I've put out 2 releases as public betas and had quite a lot of>feedback on which to base Ver3. I think Ver3 is ready but just>want to be sure, its very hard to spot your own mistakes!!Jim, I know how that is, as 43 years old systems developer, and believe me you'll never spot every bug no matter how hard you try even with a beta testing team. The best beta testing, nowadays when there are so many hardware and software configurations that may be of influence, is to relase it like you did with your previous versions, so everyone interested can try it. You can see it doing even by the greatest software companies :-hah>Other people have e-mailed me with the same "No File Opened">problem. It has usually been because the PLN file was either>created (or edited) by another Add-On, which alters the file>structure slightly or because the PLN has more than 25>waypoints.>If you open the PLN file using Flight Planner within MS2004,>edit it slightly, then re-save. This will restructure the PLN>file and then my Route Editor will be able to open it>(Provided its less than 25 waypoints). I wish that was the problem. After trying to open my flight plans (non of them having more then 10-15 waypoints), I thought the same like you, about possibe structure issue, and tried to open some flight plans included with FS like aerial01.pln, alaska01.pln and the problem persisted. What I think is that if FS or Radar Contact or other thirdy party tool reads the files, you're application has to be able to read it, too. Otherwise, I could think of possible difference in parsing logic.Another thing that might be useful in your development. Most people, including myself, use FSNavigator or FSBuilder as primary flight planners among others. Maybe you shoud generate some plans with those tools and test them with your application, otherwise you might recieve many bug reports ;)Hope this helps.Regards,Gig

Good old Microsoft, haven't been consistent in the data structure of their PLN files.A PLN file from the 'Flights' folder looks like this:[flightplan]title=KACK to KPVCdescription=KACK, KPVCtype=IFRroutetype=0cruising_altitude=5000departure_id=KACK, N41* 15.53', W70* 3.80', +000048.00departure_position=PARKING 1destination_id=KPVC, N42* 4.19', W70* 13.58', +000008.00departure_name=Nantucket Memldestination_name=Provincetown Munwaypoint.0=KACK, A, N41* 15.53', W70* 3.80', +000048.00, waypoint.1=KPVC, A, N42* 4.19', W70* 13.58', +000008.00, If you load this into Flight Planner (you have to copy it across from the 'Flights' folder to the 'Flight Simulator Files' folder first though) and re-save it, it then looks like this:[flightplan]AppVersion=9.1.40901title=KACK to KPVCdescription=KACK, KPVCtype=IFRroutetype=0cruising_altitude=5000departure_id=KACK, N41* 15.53', W70* 3.80', +000048.00departure_position=PARKING 1destination_id=KPVC, N42* 4.19', W70* 13.58', +000008.00departure_name=Nantucket Memldestination_name=Provincetown Munwaypoint.0=, KACK, , KACK, A, N41* 15.53', W70* 3.80', +000048.00, waypoint.1=, KPVC, , KPVC, A, N42* 4.19', W70* 13.58', +000008.00, It adds the AppVersion and all the Waypoints get a double dose of the Waypoint name!!!!I will clearly state in my ReadMe file that the Route Editor is ONLY for editing PLN created using Flight Planner. After all that is why I wrote it, I wanted to create a new route then go in an edit it.Any existing PLN files can be read if they are first loaded into Flight Planner then re-saved. Bear in mind that Flight Planner will only read from the 'Flight Simulator Files' folder.RegardsJim

Hi Jim,I don't see too much problem in checking if "AppVersion" line exists and use one parsing logic, and if not other one. The problem in loading the flight plan is that you can't simply load it and save, but have to use the find route button in order to be able to save it and once done that, FS could change considerably your original flight plan, even the cruising altitude. So, I consider that this utility is trictly for users of the in-built FS planner.Anyway, my personal opinion, others may disagree. Having FSNavigator and FSBuild, why would I have to plan, save, load, resave, load, modify, save; just to make a small modification when I can do that in one step with those flight planners.If I were you, I wouldn't stick just to one flight .pln format, especially when all others planners exports to a FS different, but to similar one. This would avoid narrowing your "audience" from the begining.Anyway, thanks for your time and wish you the best in your work.Regards,Gig

Gig,Agreed!This was originally for people who only used Flight Planner. However, once Pandora's box has been opened.......So I have spent the last couple of hours writing the sub-routines that cater for BOTH types of PLN files.RegardsJim

Glad to hear that Jim and also glad to help. Here is your request:{flightplan} (Had to change the brackets)title=SUMU to SABEdescription=SUMU, SABEtype=IFRroutetype=1cruising_altitude=15000departure_id=SUMU, S34* 50.27', W56* 1.82', +000104.99departure_position=GATE C 0destination_id=SABE, S34* 33.53', W58* 24.98', +000016.40departure_name=Carrasco Intl/Gen C L Berissodestination_name=Jorge Newbery Aeroparquewaypoint.0=SUMU, A, S34* 50.27', W56* 1.82', +000104.99,waypoint.1=DAGUS, I, S35* 2.28', W56* 7.42', +000000.00,waypoint.2=SARGO, I, S34* 58.97', W56* 53.03', +000000.00,waypoint.3=PAGON, I, S33* 55.27', W58* 43.23', +000000.00,waypoint.4=VANAR, I, S34* 19.47', W58* 45.73', +000000.00,waypoint.5=FDO, V, S34* 27.08', W58* 35.05', +000000.00,waypoint.6=SABE, A, S34* 33.53', W58* 24.98', +000016.40,Regards,Gig

Thanks Gig,This falls into the 'Flights' category rather than the 'Flight Planner' categoryHopefully there are only 2 types of PLN files out there!!RegardsJim

Another one:{flightplan}title=SUMU to SABEdescription=SUMU, SABEtype=IFRroutetype=3cruising_altitude=14000departure_id=SUMU, S34* 50.15', W056* 01.49',+000105.00departure_position=01destination_id=SABE, S34* 33.37', W058* 24.55',+000020.00departure_name=MONTEVIDEO_CARRASCO_INTLdestination_name=AEROPARQUE_JORGE_NEWBERYwaypoint.0=SUMU, A, S34* 50.15', W056* 01.49', +000000.00, waypoint.1=SARGO, I, S34* 58.58', W056* 53.02', +10000.00, waypoint.2=ESLAN, I, S34* 58.55', W057* 05.05', +12000.00, waypoint.3=PTA, V, S34* 58.33', W057* 53.54', +14000.00, waypoint.4=EZE, V, S34* 49.26', W058* 32.07', +14000.00, waypoint.5=ENO, V, S34* 33.46', W058* 47.26', +11000.00, waypoint.6=VANAR, I, S34* 19.28', W058* 45.44', +06000.00, waypoint.7=SABE, A, S34* 33.37', W058* 24.55', +000000.00,

And the last one I've seen, but don't pay too much attention on this one, because is the least used:{Flightplan}title=SUMU to SABE description=SUMU, SABE type=IFRroutetype=3cruising_altitude=28000departure_id=SUMU, S34* 50.09', W056* 01.50', +000105.00departure_position=06destination_id=SABE, S34* 33.53', W058* 24.98', +000016.00departure_name=Carrasco Intl/Gen C L Berissodestination_name=Jorge Newbery Aeroparquealternate_name=waypoint.0=SUMU, A, S34* 50.09', W056* 01.50', +000105.00,waypoint.1=KKNIMBO, I+LOCWAY, S34* 30.82', W056* 29.53', +000000.00,waypoint.2=KKPABOT, I+LOCWAY, S34* 15.60', W056* 51.57', +000000.00,waypoint.3=KKPONPA, I+LOCWAY, S33* 56.42', W057* 18.98', +000000.00,waypoint.4=KKPAPIX, I+LOCWAY, S34* 24.97', W058* 00.03', +000000.00,waypoint.5=SABE, A, S34* 33.53', W058* 24.98', +000016.00,Happy programming :)

Hi Jim. sent you a lengthy PM reply with some feedback on my beta testing of version 3. cheers.