Content Options doesn't work on parent folder

Issues 2508 Goose
1

I have my games organised into systems and genres, eg:

snes
  Action
    Wild Guns.smc
  RPG
    Final Fantasy VI.smc

psx
  Driving
    Gran Turismo.chd
  Tactical RPG
    Final Fantasy Tactics.chd

In Pixie I used to be able to browse to the system directory (eg: SNES, Playstation) and press Select to bring up Content Options, then I could select a core and set that core recursively so that all games in the one system used the same core.

In Goose, I can no longer choose a core recursively from the system directory, I need to go into each genre directory and set the core in each directory. There are a lot of genre directories across all systems so this is a lot of manual work.

Is it possible to add back the ability to set core recursively from a system folder?

2

Can you try putting a game in the root folder then with that game selected try assigning the core recursively

3

Thanks for the quick reply!

That does work, but I would prefer not to have a dummy ROM in each directory just for this purpose. This worked well in Pixie so it kinda seems like a step backwards to need to do that.

4

Correct me if I’m wrong but we never allowed changing content options when selecting a directory in Pixie. You also don’t need to keep the dummy file in there, just delete it once you’re done with it.

5

I just double checked. It is there in Pixie but not in Goose.

Pixie with Content Option on directory: https://imgur.com/NFp0yxQ

Canada Goose wth Content Option on directory: https://imgur.com/0SQhDcN

(having taken photos i now see there is a menu screenshot hotkey, oh well, now i know for next time)

1 Like
6

I’ll take a look when I get a chance, I have some ideas for this

2 Likes
7

Well then, I stand corrected! :dogheh:

1 Like
8

Just skimming the code, this appears due to f1d19a5 Fixed options navigation generation issue which moved the check like:

const char *dot = strrchr(rom_name, '.');
if ((dot && dot != rom_name)) {
    INIT_VALUE_ITEM(-1, option, Core, lang.MUXOPTION.CORE, "core", "");
    INIT_VALUE_ITEM(-1, option, Governor, lang.MUXOPTION.GOVERNOR, "governor", "");
    INIT_VALUE_ITEM(-1, option, Tag, lang.MUXOPTION.TAG, "tag", "");

It seems as if the current behaviour was the original intention, and the fact this appeared in Pixie was a bug that I enjoyed while it lasted :stuck_out_tongue:

I have a different suggestion than changing this in the UI module.

I see there is a lot of handling of default content paths like snes or Nintendo - SNES-SFC or whatever the names are. Would it be better to recursively set a default emulator for those known paths?

That would handle arbitrary subfolders automatically. Then if someone wants to change the emulator for a specific game, they can do that by pressing Select on the game.

I assume the common use case for changing emulator is for specific games, not for all games on a system.

9

I still want to fix the being able to assign a core while on a folder but I’ll consider the the recursive auto assign too.

1 Like
10

after giving it some thought we won’t be doing the auto recursive assign as this would not work well for scenarios where people organize their content by /manufacturer/system/

I will be making a change that if you have a folder highlighted and hit select then you can assign a core or governor to that directory or recursively to that directory.

1 Like
11

Sounds good! Thank you for looking into it.

12

The following has been added…

Will be available in the upcoming 2508.2 Silly Goose patch release.

1 Like
13

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.