New map presentation

[brunodles]

Description

Changes how the map is presented.
Instead of using the "inverted" presentation, it will only present the letters, making it less "blocking".
This will also change the colors used to create the map, making it closer to the row indicators.
The selected cursor also changed.

Depends on pr #270.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Test Configuration: Linux X64

• Hardware: Intel PC
• Test steps:
  1. open a project
  2. navigate through all the pages

Checklist:

• I have performed a self-review of my code
• I have commented particularly in hard-to-understand areas
• I have updated CHANGELOG
• I have updated docs/wiki/What-is-LittlePiggyTracker.md reflecting my changes
• I have version bumped in sources/Application/Model/Project.h
• My changes generate no new warnings (build without your change then apply your change to check this)

Notice

This is kinda of a draft, I will love to hear feedback on how should be be configured:

1. create a new color configuration for each option, including the invert
2. create a new configuration to enable this
3. something else?

Because of that I have not completed the checklist or updated the CHANGELOG.

[djdiskmachine]

Hey this looks kinda interesting!
What are you looking to configure? If we decide to go with this we go and move forward, not look back.
Do you think you could have a look at the themer as well? https://littlepiggytracker.github.io/themer/index.html

[brunodles]

What are you looking to configure?

The colors and how it is presented. How much customization we want to allow or if it should be reversible.

Option 1 - Detailed config

As it have 3 levels of representation

1. Disabled - the user cannot navigate into them from the current position
2. Nearby - around the selected one, user can navigate into it
3. Selected - the current screen

Combined with 2 configurations per representation (color, inverted), the user will be able to change in multiple different ways.
Can allow users to change it in ways we have not planed.

• making the disabled_color same as background it will look like it was not draw in the screen
• or unintended make it "invisible"

It could end up with 6 new properties on the configuration file.
The issue is that will introduce a lot of configurations on the theming. I'm a bit afraid on how it would affect the old devices (I get a a lot of win32 errors on my fork).

Option 2 - New version, new mode

Change it for everyone.

If we decide to go with this we go and move forward, not look back.

You got into the point, I was worried to include something that might not please the users.

Option 3 - Switcher

Changes between the old and the new.

Do you think you could have a look at the themer as well?

Yes, I'm planning to include it in the following steps, which include some other visuals changes.

1. Redesigning the project view

• Project View redesign brunodles/LittleGPTracker#17.

2. Create a Config View

• also built on top of the map redesign
• The idea was to separate the lgpt configuration from project configuration
• For example, the midi and the auto-load could be part of this configuration
• which would also include the theme at some moment, I was working to make it, but it was not ready.

3. Create Theme

• this one is not ready, but I have an issue to get back into it
• [IDEA] - Create themes for lgpt brunodles/LittleGPTracker#4
• This would introduce the ability to switch themes (files).

4. Theme editor

• Just planning for now. I have not implemented this on my tests.

This is what I have on my wip branch

I've been testing on my fork, just to get familiar with the code base, but I'm feeling confidant to open the PRs in next weeks.

Screencast.From.2026-08-18.22-36-16.mp4

• https://github.com/brunodles/LittleGPTracker/tree/wip
• [IDEA] - Create themes for lgpt brunodles/LittleGPTracker#4

I will break those into small changes, to make it fit better in this repo and not conflict with the work that the rest of the community is already doing.

But as you can see in the video, I was already working on the theme selector.

[djdiskmachine]

Oh damn that's fantastic!
Yeah for sure, we'll go down this route it looks very promising. The only little nitpick I have is the "detect root" function (very useful, love it!) might belong in its own screen/dropdown/selector.. I have some ideas of FX I'd like to add in the instrument screen but we can take it from there when we get there.

In-pig config is amazing, I'd love to be able to drop maintaining the web configer tbh =D

Love to see some visual re-vamping, just be aware that I don't have so much time right now and I'd really like to get to some sort of release stage of 1.6.0 before we move forward. I'm hoping the winter months will be better, I'm usually more productive with piggy between November-february as the weather over here doesn't exactly inspire going out. =D

As for indicating items in the map that aren't possible to navigate to - depends on the purpose I guess? To me it's visually intuitive enough that you can't go from S to T for example but maybe I'm just home blind and not understanding the issue?
If it's necessary, could we just make it slightly darker than the other items on the row? Or indicate it with a "-"?

Anyway, thanks again can't wait to see what this turns into :)