Control Surface Integration (CSI) Technical Feature Discussion - Page 462

Funkybot · 08-10-2022, 01:38 PM

Quote:

Originally Posted by Geoff Waddington

Yup, to be honest I haven't thought through the details yet, but I envision it similar to how EuCon works with the Mix rotaries, when you bank.

For those not familiar with that, think Track banking, but instead of offsets from Track 1, it's offsets from param 0.

I was thinking banks/pages would just be "subzones" with "Next" and "Previous" actions for navigation. For instance, if a plugin had 53 params, and 16 widgets in the .mtp file, CSI would create....

LX480-1.zon (first 16 params)
LX480-2.zon (next 16 params)
LX480-3.zon (next 16 params)
LX480-4.zon (final 5 params)

Then inside each would be one or two rows to facilitate (i.e. "fake") banking. But all it would do is just cycle through the sub-zones.

...my thinking with that was "maybe Geoff has to build very little new and just leverage how CSI already works".

MixMonkey · 08-10-2022, 01:41 PM

Quote:

Originally Posted by Funkybot

I was thinking banks/pages would just be "subzones" with "Next" and "Previous" actions for navigation. For instance, if a plugin had 53 params, and 16 widgets in the .mtp file, CSI would create....

LX480-1.zon (first 16 params)
LX480-2.zon (next 16 params)
LX480-3.zon (next 16 params)
LX480-4.zon (final 5 params)

Then inside each would be one or two rows to facilitate (i.e. "fake") banking. But all it would do is just cycle through the sub-zones.

...my thinking with that was "maybe Geoff has to build very little new and just leverage how CSI already works".

Exactly my thinking too

Navelpluisje · 08-10-2022, 02:05 PM

Quote:

Originally Posted by MixMonkey

Exactly my thinking too

That makes 3 of us

Funkybot · 08-10-2022, 02:05 PM

Quote:

Originally Posted by MixMonkey

Exactly my thinking too

The other benefit to that type of approach is that it's still easy to move a parameter from the LX480-3.zon to the LX480-1.zon and follows a familiar syntax.

Also, Geoff, as I'm thinking about the .mtp/.otp design idea, I'm starting to have some concerns creep in. How does CSI know to add in displays?

For instance, instead of an .mtp/.otp file, if we used a Generic_FX.zon we could do this to pair the displays with the params:

Code:

DisplayUpper1      FXParamNameDisplay 1
DisplayLower1      FXParamValueDisplay 1
Fader1             FXParam 1

That's probably the most basic example with displays. How would the .mtp/.otp approach say, "this display goes with this control?"

I'm thinking if starting with a "generic_fx.zon", that would offer users more control but get us to a similar place. A user could even hypothetically do something like this if they wanted pressing Shift to expose what was assigned to the Rotary...

Code:

Fader1                   FXParam 1
DisplayUpper1            FXParamNameDisplay 1
DisplayLower1            FXParamValueDisplay 1

Rotary1                  FXParam 2
Shift+DisplayUpper1      FXParamNameDisplay 2
Shift+DisplayLower1      FXParamValueDisplay 2

...just thinking out loud here.

MixMonkey · 08-10-2022, 02:33 PM

Quote:

Originally Posted by Funkybot

For instance, instead of an .mtp/.otp file, if we used a Generic_FX.zon we could do this to pair the displays with the params

I was thinking along those lines too, that it might be easier to create a generic FX Zone for each surface and fit the FX parameter indices into it, but I guess this is moving the whole thing back the manual Zone creation paradigm that Geoff is trying to get away from.

Freex · 08-10-2022, 02:38 PM

Personally I'd be happy for CSI to auto map unmapped FX

But I wouldn't want it to start saving every FX that's not mapped.

That $hit would get old fast, and surely next time round its not an unmapped FX it's got a random linear map.

Just give me a generic map, let me know I've been lazy and not sorted that FXs map out, and more on.

MixMonkey · 08-10-2022, 02:43 PM

Quote:

Originally Posted by Freex

Personally I'd be happy for CSI to auto map unmapped FX

But I wouldn't want it to start saving every FX that's not mapped.

That $hit would get old fast, and surely next time round its not an unmapped FX it's got a random linear map.

Just give me a generic map, let me know I've been lazy and not sorted that FXs map out, and more on.

I think the idea is that this is instead of actually creating a map, just an on the fly mapping that happens if there is no map saved.

Freex · 08-10-2022, 03:15 PM

Quote:

Originally Posted by MixMonkey

I think the idea is that this is instead of actually creating a map, just an on the fly mapping that happens if there is no map saved.

That's what I thought to idea was, but then I see FXname.zon-1, FXname.zon-2, FXname.zon-3 etc, and that looks like an automatic map generator.

Which would be awful. IMHO

I assumed there would just be a "generic.zon" for your surface of choice and that's going to do the needful.

Geoff Waddington · 08-10-2022, 03:45 PM

Great discussion !

I'm starting to like the idea of SubZones for navigation.

Also liking the "no save" approach.

As far as pairing the displays, we can probably use the .mst/.ost names themselves.

Matter of fact as long our naming conventions are solid, we may not even need .mpt/.opt files.

We can look for Widgets named Fader, Rotary, RotaryPush, DisplayUpper, DisplayLower, etc, and dodge the extra file.

We can also look for things that have numbers appended, Fader1, Fader2, etc.

We can make the assumption the we first try to display the param name, and if there is more than one display, we can also show param value.

And to Freex's point, maybe we do this entirely dynamically, never saving the .zon files, so as not to clutter up the Zones folders.

One of the things that may happen with the generic FX Zone is unwanted coupling of a Widget type to a param.

Navelpluisje's experiment shows we may be able to separate switches out.

In that case, having the freedom to assign any param to any Widget may be better than the somewhat hardwired generic FX Zone approach.

Just some more thoughts.

And just have to say what a great community we have here !

MixMonkey · 08-10-2022, 03:55 PM

Quote:

Originally Posted by Geoff Waddington

I'm starting to like the idea of SubZones for navigation.

Also liking the "no save" approach.

Pretty sure these are mutually exclusive and represent the two schools of thought on the matter

Geoff Waddington · 08-10-2022, 04:17 PM

Quote:

Originally Posted by MixMonkey

Pretty sure these are mutually exclusive and represent the two schools of thought on the matter

I must be missing something, I don't understand why.

Funkybot posted:
'I was thinking banks/pages would just be "subzones" with "Next" and "Previous" actions for navigation. For instance, if a plugin had 53 params, and 16 widgets in the .mtp file, CSI would create....

LX480-1.zon (first 16 params)
LX480-2.zon (next 16 params)
LX480-3.zon (next 16 params)
LX480-4.zon (final 5 params)

Then inside each would be one or two rows to facilitate (i.e. "fake") banking. But all it would do is just cycle through the sub-zones.

...my thinking with that was "maybe Geoff has to build very little new and just leverage how CSI already works" '

We could easily generate these dynamically and never save them.

MixMonkey · 08-10-2022, 04:24 PM

Quote:

Originally Posted by Geoff Waddington

We could easily generate these dynamically and never save them.

No, I'm the one that's missing something

I automatically associated creating SubZones with actually saving them. Of course they can be created in memory and stay there.

jacksoonbrowne · 08-10-2022, 04:53 PM

On the CSI wiki, when I click on the link: Examples that come with the beta download
It brings me to the reaper stash with "The requested file does not exist."

I did find the files @ https://stash.reaper.fm/v/44740/CSI%...rt%20Files.zip

Funkybot · 08-10-2022, 05:04 PM

Quote:

Originally Posted by jacksoonbrowne

On the CSI wiki, when I click on the link: Examples that come with the beta download
It brings me to the reaper stash with "The requested file does not exist."

I did find the files @ https://stash.reaper.fm/v/44740/CSI%...rt%20Files.zip

Just updated the link. Thanks for reporting!

Funkybot · 08-10-2022, 05:08 PM

Quote:

Originally Posted by Geoff Waddington

We could easily generate these dynamically and never save them.

Can we [I mean the "royal we" as in "Geoff" - please

] make saving optional? I think someone may have a pretty good auto-map and want to tweak it manually for the final finishing touches. I'm thinking a CSI action to optionally create .zon files would be nice. But LOVE the idea of this happening dynamically!

AtmanActive · 08-10-2022, 05:08 PM

ToggleScrollLink was recently changed to default to OFF.

How do I make it ON by default for me and my surface?

I tried:

Code:

Zone "Home"
	
	OnInitialization ToggleScrollLink

but it doesn't seem to be working.

Geoff Waddington · 08-10-2022, 05:11 PM

Quote:

Originally Posted by Funkybot

Can we [I mean the "royal we" as in "Geoff" - please

] make saving optional? I think someone may have a pretty good auto-map and want to tweak it manually for the final finishing touches. I'm thinking a CSI action to optionally create .zon files would be nice. But LOVE the idea of this happening dynamically!

Yeah, I'm also thinking it should be optional to save it.

This gives us the option not to clutter up the Zone folders arbitrarily, but if we like a particular plugin, and do want to make it a Zone (Zones), we can.

Geoff Waddington · 08-10-2022, 05:12 PM

Quote:

Originally Posted by AtmanActive

ToggleScrollLink was recently changed to default to OFF.

How do I make it ON by default for me and my surface?

I tried:

Code:

Zone "Home"
	
	OnInitialization ToggleScrollLink

but it doesn't seem to be working.

Thanks for testing, will investigate.

Geoff Waddington · 08-10-2022, 06:24 PM

Quote:

Originally Posted by AtmanActive

ToggleScrollLink was recently changed to default to OFF.

How do I make it ON by default for me and my surface?

I tried:

Code:

Zone "Home"
	
	OnInitialization ToggleScrollLink

but it doesn't seem to be working.

Just tried it here and it works just fine.

Toggle Scroll Link ensures that the Selected Track is visible on the Control Surface.

If it is already visible on one of the Control Surface Channels, nothing happens.

If it not visible, it is made the left most Channel on the Control surface, unless you are near/at the end of your Tracks, then it is made whatever is appropriate to ensure the last Track is on the last Channel.

Is this not what you are seeing ?

WaveTrans · 08-11-2022, 12:59 AM

Hi, Geoff,

sorry if this is not the right time for a reminder but this last post reminded me of the feature request I should remind you off (CSI: Devices...thread (post #2470))

Request was Broadcast/Recieve of Banking Actions and ToggleEnableFocusedFXMapping

@MixMonkey described it in more detail in post # 2467 (CSI: Devices... thread)

Thanks, WT

Navelpluisje · 08-11-2022, 03:20 AM

Quote:

Originally Posted by Geoff Waddington

Matter of fact as long our naming conventions are solid, we may not even need .mpt/.opt files.

I do not completely agree on this. Not all displays have 2 rows. The FaderPort has up to 4 and I think the MCE24 also. Both also have different display types. (FaderPort currently not in v2, but am working on it).

That's why I had this part in my proposal:

Code:

  ScribbleLine1_|    FXToggleParamNameDisplay
  ScribbleLine2_|    FXToggleParamValueDisplay
  ScribbleLine3_|    FXParamNameDisplay
  ScribbleLine4_|    FXParamValueDisplay

Navelpluisje · 08-11-2022, 03:24 AM

Quote:

Originally Posted by Geoff Waddington

And to Freex's point, maybe we do this entirely dynamically, never saving the .zon files, so as not to clutter up the Zones folders.

Agree. But would it be possible to update the `CSI Toggle Write Params to /CSI/Zones/ZoneRawFXFiles when FX inserted` actionin a way that it is using the generic zone? For those who want the files and have a cool starting point WITH subzones etc.

Geoff Waddington · 08-11-2022, 04:00 AM

Quote:

Originally Posted by WaveTrans

Hi, Geoff,

sorry if this is not the right time for a reminder but this last post reminded me of the feature request I should remind you off (CSI: Devices...thread (post #2470))

Request was Broadcast/Recieve of Banking Actions and ToggleEnableFocusedFXMapping

@MixMonkey described it in more detail in post # 2467 (CSI: Devices... thread)

Thanks, WT

It's never a bad time for a reminder.

Knee deep in EuCon right now, but will get to it when possible.

Geoff Waddington · 08-11-2022, 04:01 AM

Quote:

Originally Posted by Navelpluisje

I do not completely agree on this. Not all displays have 2 rows. The FaderPort has up to 4 and I think the MCE24 also. Both also have different display types. (FaderPort currently not in v2, but am working on it).

That's why I had this part in my proposal:

Code:

  ScribbleLine1_|    FXToggleParamNameDisplay
  ScribbleLine2_|    FXToggleParamValueDisplay
  ScribbleLine3_|    FXParamNameDisplay
  ScribbleLine4_|    FXParamValueDisplay

I don't understand this.

CSI doesn't have Actions named FXToggleParamNameDisplay and FXToggleParamValueDisplay, are these Actions you have added ?

Geoff Waddington · 08-11-2022, 04:04 AM

Quote:

Originally Posted by Navelpluisje

Agree. But would it be possible to update the `CSI Toggle Write Params to /CSI/Zones/ZoneRawFXFiles when FX inserted` actionin a way that it is using the generic zone? For those who want the files and have a cool starting point WITH subzones etc.

Yes, or something like it.

We would allow the option of saving Zones/SubZones if you so wish.

We touched on this in an earlier post, although I know, it's moving very quickly, I'm having trouble keeping up myself

Navelpluisje · 08-11-2022, 04:33 AM

Quote:

Originally Posted by Navelpluisje

I do not completely agree on this. Not all displays have 2 rows. The FaderPort has up to 4 and I think the MCE24 also. Both also have different display types. (FaderPort currently not in v2, but am working on it).

That's why I had this part in my proposal:

Code:

  ScribbleLine1_|    FXToggleParamNameDisplay
  ScribbleLine2_|    FXToggleParamValueDisplay
  ScribbleLine3_|    FXParamNameDisplay
  ScribbleLine4_|    FXParamValueDisplay

True, these don't exist (yet). The idea is to make a difference between the toggle and non-toggle params. At least for the generated zone files. This way it will, at least in my head it worked, be easier to make a diference where to put what value/name.

So when a param is a toggle it feeds the Toggle actions and the regular actions otherwise. This will, also in my head, only work for (and i think only is needed) the generated zones

Geoff Waddington · 08-11-2022, 04:41 AM

Quote:

Originally Posted by Navelpluisje

True, these don't exist (yet). The idea is to make a difference between the toggle and non-toggle params. At least for the generated zone files. This way it will, at least in my head it worked, be easier to make a diference where to put what value/name.

So when a param is a toggle it feeds the Toggle actions and the regular actions otherwise. This will, also in my head, only work for (and i think only is needed) the generated zones

Ah, got it.

Yes, that would make it easy to decide whether to push or turn the Rotary, unfortunately on the Faderport series, the single Rotary

Still trying to figure out why they thought a single rotary for 16 Channels was a good idea, such a great surface otherwise...

AtmanActive · 08-11-2022, 05:29 AM

Quote:

Originally Posted by Geoff Waddington

Just tried it here and it works just fine.

Toggle Scroll Link ensures that the Selected Track is visible on the Control Surface.

If it is already visible on one of the Control Surface Channels, nothing happens.

If it not visible, it is made the left most Channel on the Control surface, unless you are near/at the end of your Tracks, then it is made whatever is appropriate to ensure the last Track is on the last Channel.

Is this not what you are seeing ?

ToggleScrollLink functionality is working as expected once I enable it manually through my surface.

What is not working is OnInitialization ToggleScrollLink in my "Home" zone.
In other words, I can't get my surface to start with ScrollLink ON. It always starts with ScrollLink OFF and I need to manually activate it by tapping my TouchOSC button that does ToggleScrollLink.
As I am using only one surface, for me it is beneficial to have ScrollLink ON by default. I do understand your reasons why you need it to be OFF by default, but I was expecting to be able to bring it back to default-ON functionality by the command OnInitialization ToggleScrollLink in my "Home" zone. That command is being ignored entirely.

Navelpluisje · 08-11-2022, 05:38 AM

Quote:

Originally Posted by Geoff Waddington

Ah, got it.

Yes, that would make it easy to decide whether to push or turn the Rotary, unfortunately on the Faderport series, the single Rotary

Still trying to figure out why they thought a single rotary for 16 Channels was a good idea, such a great surface otherwise...

True on the pans. Same goes actually for the arm button. But it is a great controller and with CSI and some lua has really endless possibilities

Geoff Waddington · 08-11-2022, 06:55 AM

Quote:

Originally Posted by AtmanActive

ToggleScrollLink functionality is working as expected once I enable it manually through my surface.

What is not working is OnInitialization ToggleScrollLink in my "Home" zone.
In other words, I can't get my surface to start with ScrollLink ON. It always starts with ScrollLink OFF and I need to manually activate it by tapping my TouchOSC button that does ToggleScrollLink.
As I am using only one surface, for me it is beneficial to have ScrollLink ON by default. I do understand your reasons why you need it to be OFF by default, but I was expecting to be able to bring it back to default-ON functionality by the command OnInitialization ToggleScrollLink in my "Home" zone. That command is being ignored entirely.

Please post your CSI.ini contents and your Home.zon contents, we'll get you sorted.

AtmanActive · 08-11-2022, 07:12 AM

Quote:

Originally Posted by Geoff Waddington

Please post your CSI.ini contents and your Home.zon contents, we'll get you sorted.

CSI.ini:

Code:

Version 2.0

OSCSurface "TouchOSC Samsung" 44153 44154 192.168.150.26
OSCSurface "TouchOSC Desktop" 64001 64002 127.0.0.1

Page "HomePage" 
"TouchOSC Samsung" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1" 
"TouchOSC Desktop" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1"

iPad__Home.zon:

Code:

Zone "Home"
	
	OnInitialization ToggleScrollLink
	OnInitialization ToggleEnableFocusedFXMapping
	OnTrackSelection Reaper _S&M_WNCLS3
	
     	IncludedZones
     	   	"Buttons"
     	   	"Track"
     	   	"SelectedTrackFXMenu"
     	   	"SelectedTrack"
		"MasterTrack"
     	IncludedZonesEnd
     
     	AssociatedZones
     		"SelectedTrackSend"
     		"SelectedTrackReceive"
     		"TrackSend"
     		"TrackReceive"	
     	AssociatedZonesEnd
		
ZoneEnd

Thanks!

Geoff Waddington · 08-11-2022, 07:51 AM

Quote:

Originally Posted by AtmanActive

CSI.ini:

Code:

Version 2.0

OSCSurface "TouchOSC Samsung" 44153 44154 192.168.150.26
OSCSurface "TouchOSC Desktop" 64001 64002 127.0.0.1

Page "HomePage" 
"TouchOSC Samsung" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1" 
"TouchOSC Desktop" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1"

iPad__Home.zon:

Code:

Zone "Home"
	
	OnInitialization ToggleScrollLink
	OnInitialization ToggleEnableFocusedFXMapping
	OnTrackSelection Reaper _S&M_WNCLS3
	
     	IncludedZones
     	   	"Buttons"
     	   	"Track"
     	   	"SelectedTrackFXMenu"
     	   	"SelectedTrack"
		"MasterTrack"
     	IncludedZonesEnd
     
     	AssociatedZones
     		"SelectedTrackSend"
     		"SelectedTrackReceive"
     		"TrackSend"
     		"TrackReceive"	
     	AssociatedZonesEnd
		
ZoneEnd

Thanks!

Aha, thought that might be the case, that's why I asked for your CSI.ini

You are using the same Zone folder for both surfaces.

Think about what happens.

When "TouchOSC Samsung" comes online, its Home Zone activates and the ToggleScrollLink Action is executed.

Now, when "TouchOSC Desktop" comes online, its Home Zone activates and the ToggleScrollLink Action is executed.

ToggleScrollLink isn't being ignored, it is being executed twice.

Just use different Zone folders for the two surfaces, one with the OnInitialization ToggleScrollLink and one without.

On our end we should do a better job of documenting and emphasizing that the ToggleScrollLink is actually a Page level Action, not a Surface level Action, it's unique in that characteristic.

Thanks for pointing this out, those of us who have been around a while likely recall that ScrollLink used to be a checkbox option in the Page config GUI, so it is clear to us how it needs to be defined, our collective bad on that one

AtmanActive · 08-11-2022, 08:13 AM

Quote:

Originally Posted by Geoff Waddington

Aha, thought that might be the case, that's why I asked for your CSI.ini

You are using the same Zone folder for both surfaces.

Think about what happens.

When "TouchOSC Samsung" comes online, its Home Zone activates and the ToggleScrollLink Action is executed.

Now, when "TouchOSC Desktop" comes online, its Home Zone activates and the ToggleScrollLink Action is executed.

ToggleScrollLink isn't being ignored, it is being executed twice.

Just use different Zone folders for the two surfaces, one with the OnInitialization ToggleScrollLink and one without.

On our end we should do a better job of documenting and emphasizing that the ToggleScrollLink is actually a Page level Action, not a Surface level Action, it's unique in that characteristic.

Thanks for pointing this out, those of us who have been around a while likely recall that ScrollLink used to be a checkbox option in the Page config GUI, so it is clear to us how it needs to be defined, our collective bad on that one

Ah well, that's a limitation then, right there: users can't have two surfaces using same surface data. I want to have my surface next to my control room, and I want to have another surface, but behaving absolutely the same, next to my studio room. This will be a pretty legit request from a lot of users.
So it is about ToggleScrollLink which is unique in that way that it is global, even if we treat it as local, per surface.

Maybe accept an argument for ToggleScrollLink? So, with no argument, behaves absolutely the same as it is now. But, with an argument of 0 or 1, it doesn't toggle, but sets it to OFF or ON respectively. Just thinking out loud here.

Geoff Waddington · 08-11-2022, 08:27 AM

Quote:

Originally Posted by AtmanActive

Ah well, that's a limitation then, right there: users can't have two surfaces using same surface data. I want to have my surface next to my control room, and I want to have another surface, but behaving absolutely the same, next to my studio room. This will be a pretty legit request from a lot of users.
So it is about ToggleScrollLink which is unique in that way that it is global, even if we treat it as local, per surface.

Maybe accept an argument for ToggleScrollLink? So, with no argument, behaves absolutely the same as it is now. But, with an argument of 0 or 1, it doesn't toggle, but sets it to OFF or ON respectively. Just thinking out loud here.

Well, it's really a design flaw in CSI, but there is a simple workaround.

You can have the two surfaces almost the same, with the exception of the double Scroll Link trigger by copying the contents of "AA_iPad_Mixer_v1" to another Zone folder, let's name it "AA_iPad_Mixer_v1_NoScrollLinkToggle" and removing one line only, "OnInitialization ToggleScrollLink" in the copied version.

I know it's ugly, but will work for now:

Code:

Version 2.0

OSCSurface "TouchOSC Samsung" 44153 44154 192.168.150.26
OSCSurface "TouchOSC Desktop" 64001 64002 127.0.0.1

Page "HomePage" 
"TouchOSC Samsung" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1" 
"TouchOSC Desktop" 16 0 "AA_iPad_Mixer_v1.ost" "AA_iPad_Mixer_v1_NoScrollLinkToggle"

I would say a better option than ToggleScrollLink with a parameter would be a new Action, SetScrollLink that takes a parameter, "On" or "Off".

It would still be possible to get 2 Surfaces "fighting", but it would be preferable to what we have now.

Will also consider putting it back in the Page config.

MixMonkey · 08-11-2022, 08:33 AM

Quote:

Originally Posted by AtmanActive

Ah well, that's a limitation then, right there: users can't have two surfaces using same surface data.

It’s not the same surface data though is it? You want one to initialise with ScrollLink on and the other with ScrollLink off. If you want two surfaces to behave identically, then by all means access the same Zone folder, but that’s not the case here.

Geoff Waddington · 08-11-2022, 08:41 AM

Quote:

Originally Posted by MixMonkey

It’s not the same surface data though is it? You want one to initialise with ScrollLink on and the other with ScrollLink off. If you want two surfaces to behave identically, then by all means access the same Zone folder, but that’s not the case here.

Well, the subtle pushback is, it's not really Surface data we're talking about, but rather Page data, in all Surface aspects they are identical

It really is a design flaw.

MixMonkey · 08-11-2022, 08:44 AM

Quote:

Originally Posted by Geoff Waddington

Well, the subtle pushback is, it's not really Surface data we're talking about, but rather Page data, in all Surface aspects they are identical

I guess that’s the price we pay for being able to ToggleScrollLink from within the surface Zone. As you say, it used to be in the Prefs

Funkybot · 08-11-2022, 08:47 AM

For now, I've updated the Wiki with this information. If it eventually goes back to being a Page preference, then I can modify.

https://github.com/GeoffAWaddington/...gglescrolllink

AtmanActive · 08-11-2022, 08:56 AM

Quote:

Originally Posted by MixMonkey

It’s not the same surface data though is it? You want one to initialise with ScrollLink on and the other with ScrollLink off. If you want two surfaces to behave identically, then by all means access the same Zone folder, but that’s not the case here.

It is.

I don't see how I would ever want to have one surface with ScrollLink ON-by-default, while having another same surface with ScrollLink OFF-by-default. Once they start running, user can enable/disable at will, that's fine.

One more case where I want to have the same surface data on several surfaces is for development reasons.

Geoff Waddington · 08-11-2022, 08:59 AM

Quote:

Originally Posted by Funkybot

For now, I've updated the Wiki with this information. If it eventually goes back to being a Page preference, then I can modify.

https://github.com/GeoffAWaddington/...gglescrolllink

Thanks, it really is an issue because, outside of modifiers, TrackNavigationManager, where Scroll Link lives, is the only thing that is at a Page level, since Track banking applies to all Surfaces.

It's tricky to get just right, because there are no Widgets or Actions at a Page level.