• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Lock function

M

MarkkuS

Messages
125
Country
sweden
I have an airport loaded with aprons, runway, taxiways etc.

In the menu "Lock", I ticked "aprons".
But if I look at the properties of an apron, it's not locked.

What is wrong?
 
This seems to be a bug, Markkus. The apron is in fact locked (you can't move it), although not showing this in the properties. Is that true for you as well?
 
No this is not a Bug. Apron and Runway locking done from the main menu is done at application level and will always be in effect for any airport you load. The flag shows that the apron has been locked by the user.

Maybe needs explaining better or perhaps an indicator on the main status bar
 
I think it's confusing to have two different lock functions. I was misled and I sure others will be also.

An improvement would be if there was a global lock status indicator in the top window field. It should always be visible and not hidden behind a menu item. And if the global lock is set on aprons or runways, the individual properties should also reflect the global lock status.

But I also thinks there are something wrong with the current logic for the lock function.

I tried to delete an apron, but that wasn't possible. The apron could not be moved either. In the apron properties, the lock wasn't set and in the menu apron lock was not ticked. I'm not 100 percent sure how I managed to unlock the apron, but I think I did following: Selected the apron edit mode and then cancelled the edit. In the the properties, the apron lock was now set and could be ticked off.

So it's possible to get a mismatch between the actual lock status and the indicators of the lock.
 
MarkkuS said:
I think it's confusing to have two different lock functions. I was misled and I sure others will be also.

An improvement would be if there was a global lock status indicator in the top window field. It should always be visible and not hidden behind a menu item. And if the global lock is set on aprons or runways, the individual properties should also reflect the global lock status.

But I also thinks there are something wrong with the current logic for the lock function.

I tried to delete an apron, but that wasn't possible. The apron could not be moved either. In the apron properties, the lock wasn't set and in the menu apron lock was not ticked. I'm not 100 percent sure how I managed to unlock the apron, but I think I did following: Selected the apron edit mode and then cancelled the edit. In the the properties, the apron lock was now set and could be ticked off.

So it's possible to get a mismatch between the actual lock status and the indicators of the lock.
Click to expand...

Well what you describe is more or less how the group lock/unlock should work. A program level lock done from the menu bar will not affect the lock status of individual objects since it operates at the application level and not at the object (apron or runway level). The indicator shows whether or not an individual object is locked by the user and is stored in the actual ade project file for that object. Program level lock status is stored in the program settings.

Locking something is generally intended to stop it being moved or deleted by accident but no to stop editing. If you want lock to stop edits then there is an option in settings to do that.

Nevertheless your point is good and we will look at the overall arrangements for locking and unlocking objects
 
You must log in or register to reply here.
Back
Top