View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008973ardourfeaturespublic2022-09-27 10:172022-09-29 11:56
Reporterjohne53 Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status newResolutionopen 
PlatformMicrosoftOSWindowsOS Version10
Product VersionMixbus 8.x 
Summary0008973: Inconsistent Snap options
DescriptionIn Mixbus's Editor window, just above the rulers, there's a button saying 'Snap' and to the right of it there's another button offering the various Grid options. And the Edit menu (Edit->Snap & Grid) also contains a list of Grid options. For the most part, selecting an option in one menu will reflect the same option in the other.

Unfortunately though... the two menus offer different options so sometimes, selecting an option in one menu will leave the other menu showing no selection. Is that intentional or do the two menus need to be brought into sync?

Or maybe one of them isn't needed any more ?
TagsNo tags attached.

Activities

johne53

2022-09-29 11:56

reporter   ~0026590

I found this early return in 'gtk2_ardour/editor.cc' which I thought might be causing the problem:-

bool
Editor::grid_type_is_musical(GridType gt) const
{
    switch (gt) {
    case GridTypeBeatDiv32:
    case GridTypeBeatDiv28:
    case GridTypeBeatDiv24:
    case GridTypeBeatDiv20:
    case GridTypeBeatDiv16:
    case GridTypeBeatDiv14:
    case GridTypeBeatDiv12:
    case GridTypeBeatDiv10:
    case GridTypeBeatDiv8:
    case GridTypeBeatDiv7:
    case GridTypeBeatDiv6:
    case GridTypeBeatDiv5:
    case GridTypeBeatDiv4:
    case GridTypeBeatDiv3:
    case GridTypeBeatDiv2:
    case GridTypeBeat:
    case GridTypeBar:
        return true; // <--- returns early !!!
    case GridTypeNone:
    case GridTypeTimecode:
    case GridTypeMinSec:
    case GridTypeCDFrame:
        return false;
    }
    return false;
}

However, I rebuilt with that line commented out but it didn't change anything. I've also discovered that this affects both Mixbus and Ardour but the bit I'm not sure about is whether it's intentional.

Issue History

Date Modified Username Field Change
2022-09-27 10:17 johne53 New Issue
2022-09-29 11:56 johne53 Note Added: 0026590