We have to back up and think about the problem in a very general way.
Here's the deal.
Basically, this screen represents a lot of individual decisions. Each decision has three variables:
1. Which WoW has the focus.
2. Which WoW is the target.
3. Which key gets pressed.
These things are represented graphically as:
1. The WoW on the left.
2. The WoW on the right.
3. The line (row) of the spreadsheet.
To make this post easier to understand, let's pretend the user has five WoWs on the same PC.
There can be five WoWs on the left.
There can be five WoWs on the right.
In addition, the user might want to set a default for any WoW being on the left.
In addition, the user might want to set a default for any WoW being on the right.
That's 36 permutations.
I've said a couple of times that I think the program should use the metaphor of "nested" settings to simplify things, where one setting is a default and another setting "inherits" and "overrides" the default.
I know this sounds jargony and complicated but the idea is actually simple, and if it's used throughout the program, and if the screens represent the idea in a good graphical way, I think it might be the easiest thing.
So here's what I'm coming up with.
Fursphere's drawing gets simplified. It has a new basic form with only two columns. The column on the left is the default for the focus WoW. The column on the right is the default for the target WoW.
In other words, if the user only uses those two columns, they define what happens when any WoW is in the foreground (left) and what gets received by all WoWs (right).
But if the user wants, he or she can add columns on either the left or right for individual WoWs.
Once columns are added, the user can click on them to highlight them.
When that happens, it sets the permuation for the entire table.
Actually I'm not sure that works -- I need to drink a cup of coffee and draw some examples.![]()
Connect With Us