Bad registration

[rstork]

Hi,

when editing aircraft profile which I created last year, updated application version refuses to save the data with error message "Bad registration ....". The registration remains the same, I have changed just fuelflow. If I change the registration to e.g. "OK-AUO01" the application saves the data but logbook can't work with records which have been created previously with "OK-AUO-01" callsign. Could you please fix the bug?

[kitercuda]

I think the valid call sign for you aircraft is OK-AUO 01, but it is impossible to save it now.
Next upgrade will enable it.

[rstork]

What is the benefit from the registration/call sign syntax control? The same issue I have been facing with user WPT definition (seems "/" is prohibited). I would suggest to remove this kind of restrictions. Thanks a lot.

[kitercuda]

This is because of future connecting to another aviation systems. For example planefinder do not accept "bad" registration.
Now you can use OK-AAA 01. If registration is bad, application warn you, but save your aircraft...

[rstork]

Ok, your fix works fine for me. Thanks a lot!