User Activity

  • Committed [178242] on Rosegarden - Code (git)

    2023-04-02: MIDI file import fix

  • Committed [c69f92] on Rosegarden - Code (git)

    2023-03-30: Minuscule update -- missing version bump, README.md fixes

  • Committed [430d0e] on Rosegarden - Code (git)

    2023-03-29 ChordNameRuler/AnalysisTypes/ConflictingKeyChanges refactoring

  • Created ticket #1648 on Rosegarden

    Retrograde and Retrograde Invert commands broken

  • Committed [29e12c] on Rosegarden - Code (git)

    Manually restore master to being exact copy of upstream/master

  • Committed [6fe9a6] on Rosegarden - Code (git)

    2022-12-31: Pseudo-merge with rosegarden-official master [fcb8f6]

  • Committed [622e08] on Rosegarden - Code (git)

    Merge branch 'master' of https://git.code.sf.net/p/rosegarden/git

  • Posted a comment on ticket #514 on Rosegarden

    I agree that the solution lies in fixing RG's logging. The problems with that subsystem go all the way down to the fact that RG_WARNING (which should be, as per its name, for warnings) (regardless of how they might be output or not) is used throughout the code for debugging instead of RG_DEBUG or some similar, correctly-named macro/class/method/whatever. I disagree that (true) warnings shouldn't be accessible to users. Remember, I proposed that the info window would only be displayed on user command...

View All

Personal Data

Username:
thanks4opensrc
Joined:
2020-11-19 02:53:13

Projects

  • No projects to display.

Personal Tools