Why does bigbox not use launchbox settings?

[xokia]

As the title stated why does bigbox not take its settings from launchbox? Like if I hide a game in launchbox it doesnt hide in big box.

Or I setup a controller in launchbox but then have to configure bigbox seperately. It sometimes feels like having to setup to completely different front ends.
I spend a lot of time in launchbox because its PC centric and its easier to do things with a mouse and keyboard, and I have 1 usb xbox controller that I have attached.

But then when I switch it over to a TV using bigbox I tend to have to reconfigure things. Is there some reason bigbox can't be smarter and take its queues from launchbox?

[C-Beats]

10 hours ago, xokia said:

As the title stated why does bigbox not take its settings from launchbox? Like if I hide a game in launchbox it doesnt hide in big box.

Or I setup a controller in launchbox but then have to configure bigbox seperately. It sometimes feels like having to setup to completely different front ends.
I spend a lot of time in launchbox because its PC centric and its easier to do things with a mouse and keyboard, and I have 1 usb xbox controller that I have attached.

But then when I switch it over to a TV using bigbox I tend to have to reconfigure things. Is there some reason bigbox can't be smarter and take its queues from launchbox?

Because as you stated the workflows of the two applications are distinct and different. Most of the time the controller configuration (or even hide settings) don't really make sense to carry from one to the other. As stated LB is M+K centric so most don't even use controllers on it (and have a FAR inferior experience doing so) and likely since LB is the maintenance app may show otherwise hidden games so that they can still maintain them. Where BB those same games may not need to be seen (because you can't play them via controller, or just don't want people selecting it) and the whole thing is miles better with a controller. To have the two apps share settings like that is pretty counter-intuitive for what the intent and general use case of each app is and thus the settings were split.

[xokia]

6 hours ago, C-Beats said:

Because as you stated the workflows of the two applications are distinct and different. Most of the time the controller configuration (or even hide settings) don't really make sense to carry from one to the other. As stated LB is M+K centric so most don't even use controllers on it (and have a FAR inferior experience doing so) and likely since LB is the maintenance app may show otherwise hidden games so that they can still maintain them. Where BB those same games may not need to be seen (because you can't play them via controller, or just don't want people selecting it) and the whole thing is miles better with a controller. To have the two apps share settings like that is pretty counter-intuitive for what the intent and general use case of each app is and thus the settings were split.

Some of that I get but if I hide in launchbox what would be the reason someone would want to see in BigBox? Or if I tag a game as broken in launchbox it still shows up in bigbox. This is where I guess I had the false expectation that launchbox would be the "master frontend" and bigbox would be more of a "slave front end". Since bigbox is more gamer/controller centric and launchbox is more organizational centric. My time is put into launchbox organizing things, testing to make sure they work ect. The game controller is connected to launchbox because I test that things work there. I.e. launch the game from launchbox. I'm not trying to control launchbox from a game controller. When I switch over to big box with its simpler interface I want the config to be simple along with it, if its "broken" when running in launchbox it highly likely also "broken" in bigbox. Just my $.02

Edited 1 hour ago by xokia