Just wondering if anyone knows - is it possible to achieve this? Assuming "Item_A" is normally set ON (i.e. active in Community folder), I would like to activate Item_01 and have it automatically remove Item_A.

I've got a few things set up as conditional processing but I've always found that aspect a bit confusing and I don't want to risk upsetting what I've already got working.

thanks in advance for any suggestions

Hello 🍻

in the 'dependencies' right click menu, there is an option called 'Set addons to disable when this addon is enabled'. Using that on Item_01 and selecting Item_A as 'addon to disable' should do the job but note that it will work both ways -> so if you enable Item_A it will also automatically disable Item_01 if that one is enabled.

and yes it can a bit confusing even for me, i had to do a little test because i couldn't exactly what that option was doing 🙈🙃😁

Take care !

3 hours ago, Bad_T said:

it will work both ways

Great, that's even better! I thought I remembered something about this but my system has been so settled (in Addons Linker terms) for so long now I have kinda forgotten a lot of stuff about it.

But just to take the opportunity to say again that I wouldn't want to try running my system without AL. Over 800 actual addon products now, and a lot of those have multiple entries and relationships set up.

Thanks again,

Andy

Edited November 12, 20232 yr by andy1252
amended to remove autocorrection that completely changed meaning of post!

Thanks a lot for bringing up the question and to Bad_T for letting us know how to do the trick.

Very useful

5 hours ago, Bad_T said:

in the 'dependencies' right click menu, there is an option called 'Set addons to disable when this addon is enabled'.

Hi again,

I don't have this option showing on my system. I'm running version 0.18.8309.24666, and a right click on a folder gives me -
    Set dependencies for this selected addon
    Add cumulative dependencies to the selected addons
    Auto select/unselect used/unused dependencies
    Set this addon as a dependency for other addons
    Dependencies viewer

I see version 0.20.8566.36 is on .to, do I need that? I generally don't update stuff unless I need to as I don't like to risk my setup (currently showing over 4000 addons within the Linker itself!)

cheers

Yes @andy1252 i think it's a fairly recent addition so you probably need 0.20 for that option 😱

Let me know if something goes wrong but it should be safe (even recommended) to update 🤞

5 minutes ago, Bad_T said:

Yes @andy1252 i think it's a fairly recent addition so you probably need 0.20 for that option 😱

Let me know if something goes wrong but it should be safe (even recommended) to update 🤞

Thanks, I'll grab that and try it out tomorrow now. I'll let you know how it goes.

cheers

OK, so I updated the Linker to 0.20, and managed to get it to do this. Here's my setup, and I'll explain what I wanted to do.

The idea is that I'm using @guenseli's rather splendid DAMFOOL system (https://flightsim.to/file/60019/damfool-default-aircraft-management-folder-original-organization-library ) to hide all the MSFS default aircraft from the menu system. I had previously been uninstalling the ones I didn't use, because I don't like the clutter of the menu system. It works great, and it's fairly easy to create new entries for any new aircraft as they come along.

So I'll run with all the default aircraft hidden normally, but then the idea is that if I want to use one of them I would select my normal aircraft entry and load that, as I have entries for all the default aircraft in case I want to use addon liveries. In the screenshot, the idea is that I want to run a session with the default 747, which would normally be hidden because of (B). So I activate (A), and when I do that, (B) gets turned off (un-clicked) automatically.

To set up the conditional processing for this though, I had to use a sort of reverse logic. You can't (or at least, it wouldn't let me on my system) select (A) and then choose the "set addons to disable when this addon is enabled" option as it is greyed out. It seems that you can only select this for a single addon (e.g. a single one of the liveries in this case). So I selected (B), and then the required option IS available in the dependencies box, so I made (A) the "target" of (B) rather than the other way round. This now does what I want as it works in both directions, but not completely.

If I start with (A) off, and (B) enabled as my normal setup, and if I enable (A), and (B) is automatically disabled. I can then start the sim and the 747 with all its liveries is there for use.

If I disable (A) (so for my next session, perhaps), it still leaves (B) disabled. But if I enable (B), it will disable (A). This is because (B) is the subject here and (A) is the object, or at least, that's how I'd describe it.

Ideally, if I de-selected (A), then (B) would be selected automatically. This, I think, can't be done currently because you can't select a "group" folder like my (A) as the initiator of any dependencies. It can be the target, but not the originator. Don't know if that's a possible option @Bad_T? Not a major issue but it would be nice if easy to do.

But overall, I'm very happy with this. I suspect there's lots of stuff in the Linker that I just don't know about as I've got it quite happily doing all I need. I might investigate further but you know how it is, you discover stuff and then waste hours trying to think of how to use it! (or maybe that's just me)

(stop press - I just thought, would a dummy layout or manifest .json file in (A) make it selectable as an "originator" for the dependencies function? I'll have a play)

(stop press 2 - tried that, didn't work)

Edited November 13, 20232 yr by andy1252
text

Thank you for the feedback and precisions.

Yes those 'reverse dependencies' work only at 'addon' level, you can't use them on folders (just like normal dependencies).I need to check if maybe for a future version it's possible to improve that.

Thanks again 🍻