Palette search not working with custom release build

• Mar 13, 2020 - 22:33

I've run into a weird situation. I have some PRs that weren't merged, and i wanted their functionality + some more things, so I built a non-debug version of MS after merging locally. Builds fine, runs fine, but after copying over my custom workspace and having it loaded in the custom build, the resulting palette items are showing up with their own customizations with them, but the palette search function isn't correlating with them properly.

For example, if I have a palette item with name "MYNAME" and I type "MYNAME" in palette search, nothing shows up, even though the item is showing in a custom palette with "MYNAME" in it. Anyone knows what could be the problem, or if this is a known-issue? It's like MS is searching through the Basic or Advanced workspace rather than my custom loaded workspace, even though it's showing just fine...

Comments

• Mar 14, 2020 - 00:23

P.S. This is 3.5 from master branch. To be sure, even a new palette with any item added to it with a custom palette name here isn't showing up in search either. Like, if I add a treble clef to a custom palette and call it my_clef, searching for my_clef shows nothing. I wonder if this is a regression or if there's something screwy from my build.

Reply

• Mar 14, 2020 - 02:35

Update: It looks like MS3.5 (master) for me personally is only returning the names of the palettes and not the palette items. For example, I can search for "Bracket" and get the bracket palette, or Clef and get the clef palette, but if i type in treble or crescendo I get nothing. The problem lies not with custom workspaces at all as I previously imagined. I wonder if anyone can verify this on a nightly build locally.

Reply

• Mar 14, 2020 - 22:59

Thanks for responding Marc, as I was skeptical toward my own local build.

Whatever it is, it's kind of a bummer and has gotta be fixed up before the 3.5 release. Heheh, I'm kinda between a rock and a hard place: I updated my local branch PRs to fit the 3.5 code (the 127 if-else branch limit of Microsoft's compiler looks to have been fixed up within scoreview.cpp), and now if I try to build a custom 3.4.2, the branches I have won't merge with the older code base, but if I build with master, my palettes don't work with the search function. D'oh.

Reply

• Mar 14, 2020 - 23:03

Of course, it's normal that bugs sometimes get introduced between releases, and when they are caught and reported, they are virtually always fixed (such regressions are given the highest priority). So go ahead and file the issue. Feel free to try to debug it too :-), but I did already "ping" the person who msot recently worked on palette code.

Reply

Do you still have an unanswered question? Please log in first to post your question.