Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Layer 0 button/axis will fire unless they are in another?

Featured Replies

  • Commercial Member
13 minutes ago, pilotjohn said:

If I link a template, what would be the best way to "override" things when needed by quirky aircraft? This is where I thought the layers would make sense?

You got me there. At the moment, there is no solution to this, because you cannot disable parts of a linked template and/or put them on another layer. 

The whole purpose of a "link" was to avoid storing local data - which the app would have to do if you start changing layers on linked assets. I need to think about that for a while, maybe something can be done in future versions of AAO. But I don't like it.

LORBY-SI

  • Author
Just now, Lorby_SI said:

You got me there. At the moment, there is no solution to this, because you cannot disable parts of a linked template and/or put them on another layer. 

The whole purpose of a "link" was to avoid storing local data - which the app would have to do if you start changing layers on linked assets. I need to think about that for a while, maybe something can be done in future versions of AAO. But I don't like it.

Sounds good, thanks. I'll ponder this as I plan my migration. The reason I thought about it is that this is like an OO design. You have a "base" configuration, which you inherit, but can then override. I can change the base configuration which will update everything that uses it, but things that are overridden would remain so. I could then chain the inheritence if I needed to. 

  • Commercial Member
Just now, pilotjohn said:

Sounds good, thanks. I'll ponder this as I plan my migration. The reason I thought about it is that this is like an OO design. You have a "base" configuration, which you inherit, but can then override. I can change the base configuration which will update everything that uses it, but things that are overridden would remain so. I could then chain the inheritence if I needed to. 

I understand that. But you can't inherit and override like that in AAO, no way.

What could theroretically be possible is an automatic override. So when you have a linked template with a button in it and then create another assignment for the very same button input, it will use the local one instead of the linked. That should be relatively easy to do. Maybe.

 

Edited by Lorby_SI

LORBY-SI

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.