LMMS / LMMS/lmms

Odd behaviors when renaming the master mixer channel.

Open
#3,861 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug gui upstream
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

Windows 10 Pro, 64-bit OS.

GUI bugs. They happen most of the time.

They are present in RC.4, but not in master.

  • Bug 1:
    To reproduce:
  1. On the master mixer channel, double-click it or right-click it then select "Rename channel".
    The green border of the naming box isn't there.
    image
  2. Click anywhere in the mixer other than the channel itself.
  3. Do step 1 again then press enter.
    The name of the channel is highlighted in gray as if it was selected.
    image

While bug 1 is present in a project then opening a new project, the bug will be present in it.

This bug can't be undone unless LMMS is closed.

  • Bug 2:
    To reproduce:
  1. Add a mixer channel if there isn't one.
  2. Do step 1 in bug 1.
    The green border of the naming box isn't there, too.
  3. Click any mixer channel other than the master one.
    image

While bug 2 is present in a project then opening a new project, the name of the channel in the new project will be the same as the old project like this:
image

This bug can be undone by doing step 1 in bug 1, but this will result in bug 1.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing both renaming scenarios in the mixer on Windows 10, comparing RC.4 with master as described. Verify the master and added-channel naming boxes retain their green border, selection state, and names when switching projects; done means both reported behaviors are fixed without introducing the other bug.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.