Announcement

Collapse
No announcement yet.

Sub-profiles/ability for profiles to inherit a parent profile

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sub-profiles/ability for profiles to inherit a parent profile

    I started using reWASD a few weeks ago and I love it, pretty much bought it immediately. It's fantastic software.

    However, I find it kinda annoying if I want to configure profiles for specific games. This is because usually most of the profile is identical to my main profile but with one slight change. My main profile has a few configs including a radial menu.

    Sure I could clone the main profile and create a new one off it, but if I make changes to the main profile it's not reflected in the one it's cloned from. Obviously I understand that a clone is a copy, and that's fine, but the layers system has the concept of inheritance from the primary profile (in a way... I guess the layer is more a set of specific overrides). I would love it if I could create sub-profiles that inherit off a main profile in the same way a layer inherits off the top layer.

    Options that currently exist
    • Cloning a profile then making the adjustment
      • But it won't update if the profile it was cloned from changes
      • This is understandable as a clone is a copy
    • Using layers
      • This works up to a point
      • A layer can't be triggered when a process is detected
      • There's a limit as to how many layers you can have
      • Having too many layers makes config unwieldy
    • Just using one main profile and not bothering to create custom ones for specific games
    • Writing my own code that takes 2 config JSONs - a complete base and a partial override - and merges them
      • I could do this but it wouldn't integrate nicely with reWASD and would be a separate process. I also don't have the time.
    Potential solutions in a future version of reWASD
    • Implement sub-profiles which inherit off a base profile
      • Works the same way as layers off the base layer
    • Allow layers to be triggered when a process is detected
      • This could also work but config could get quite unwieldy and the layer limit would need removing
    • Global radial menu/shared radial menu concept
      • This would allow you to define a global radial menu that can be triggered from any profile

  • #2
    Hello.

    This behavior may not be suitable for all users, but thanks to your detailed description, the use case is quite clear and reasonable.

    We'll think about how to implement this, but I can't make any promises yet.

    Thank you for your suggestion.​

    Comment

    Working...
    X