Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setting the appearance of a track already at the import dialog #18687

Open
Rowin63 opened this issue Dec 7, 2023 · 1 comment
Open

setting the appearance of a track already at the import dialog #18687

Rowin63 opened this issue Dec 7, 2023 · 1 comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning

Comments

@Rowin63
Copy link

Rowin63 commented Dec 7, 2023

Describe the idea (required)

it would be a practical option, to set a tracks appearance (colour, width, ...) already at the import dialog. Now tracks are always imported with some standard settings.

Tell us about the expected behaviour (required)

it saves a step... (editing after importing)

Tell us about alternatives you've considered (required)

selecting and editing a track after importing it.

Context (optional)

Nothing essential, only an idea.
But a top improvement here would be: adding the tracks settings by the containing folder. Like: the folder determines the appearance of the contained tracks (settings belong to the folder, not the track). This would make it very easy to use tracks on different devices with the same settings (you need to set the appearance only one time, for the containing folder) .

@Dollarius
Copy link

Thank you for proposing this: I think it would be a very nice addition!
I also proposed something similar (#18616)

@vshcherb vshcherb added the Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning label Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nice to Have Should be fixed but there is no priority or no possibility to fix it within current horizon planning
Projects
None yet
Development

No branches or pull requests

3 participants