What does the "insert one bar before selection" icon in the Layout Palette ?
There is that icon in the Layout Palette
I can't understand what it does. It adds that little bar-like mark on the score. With some properties.
I couldn't find this in the handbook.
Comments
Don't confuse "Insert Measure before selection" (highlighted on Palette) with "Styff type change" (highlighted in score
In reply to Don't confuse "Insert… by Jojo-Schmitz
The highlighted mark in the score is actually what I get when I drop the one highlighted on the Palette.
In reply to The highlighted mark in the… by parkingb
Certainly not what I get when I use it
In reply to The highlighted mark in the… by parkingb
My layout palette looks different though:
![Screenshot 2023-12-26 164124.png]( "Screenshot 2023-12-26 164124.png")
In reply to My layout paslatte looks… by Jojo-Schmitz
Mine is from a fresh install of 4.2.0 :/
What do you get when you select a measure and click on the icon with a "+" (the last one), or when you drop it on a measure ?
It doesn't (and does) work for me. My palette looks like Jojo's but the "insert bar" button does the same thing as the "staff type change" button (neither of which I knew about before!)
But if you click "More" or ("Mehr"?) there is another "insert bar" icon which does work as expected.
So in the layout palette there are two identical icons - one works properly and the other does "Staff type change".
I'll start an issue since it's the same for two of us. In the meantime you can just right click anywhere and insert bars (which is what I've always done till now)
Just noticed it's "insert measure" in the nightly, and "insert bar" in the release???
In reply to It doesn't work for me… by GeoJenner
"but the "insert bar" button does the same thing as the "staff type change" button"
I've just noticed the same behavior. I also had two other icons in "More", and this one worked. I went to "Help" / Revert to Factory Settings, and everything went back to normal. "More" is empty, and the "insert measure" icon works perfectly now - see GIF below (palette display by default and behavior after resetting).
I suppose resetting only the palette concerned, via the three dots "..." on the right, should suffice?
In reply to "but the "insert bar" button… by cadiz1
Yes reset palette with the three dots worked for me.
In reply to Yes reset palette with the… by GeoJenner
For me too. Thanks !
When you say "fresh install", do you mean, a system that never previously had any version of MuseScore installed on it at any time? Or is it possible there were preferences leftover from some previous installation on this system? What OS, and how did you install it?
In reply to When you say "fresh install"… by Marc Sabatella
I should have said "A fresh update" ;-) I had previously 4.1.1 and updated to 4.2.0
In reply to I should have said "A fresh… by parkingb
OK, sounds like it was something in your custom palette definition that somehow triggered a problem. Would be interesting to see if someone can find precise to reproduce this - what specific customizations one would have to make in 4.1.1 before updating in order to trigger this.
In reply to OK, sounds like it was… by Marc Sabatella
I didn't make any customization in 4.1.1, certainly not in that palette.
In reply to I didn't make any… by parkingb
Well, the customizations are carried forward, so it could have been in any previous release. And also, the mere fact of making any customization causes your entire customized workspace to be saved, so it's just a different set of things than what happens in a fresh install. I also have customizations to other palettes but didn't see this glitch on the 4.2 update. So there has to be something quite specific about how/when you made your customizations that led to the problem. Could be the issue was with the version of the program you were using when you made the customizations, that it saved the customized palette incorrectly. Or it could be you had imported a custom palette from an incompatible version. Hard to say, really. I guess we'll see if more reports appear and a trend emerges.
In reply to Well, the customizations are… by Marc Sabatella
Pretty sure, I've never customized that Palette. Actually, I'm not using MU4.x (I'm still on MU3.7).
I'm opening MU4 only from time to time, to check if what is blocking me from using MU4.x is solved.
This time, I wanted to check an assertion that Tantacrul made on GitHub (before censoring some comments and locking some PluginAPI-related issues) that "1 year has passed and we've included a swathe of improvements since." This aroused my curiosity...
In reply to Pretty I've never customized… by parkingb
Whether you are actively using MuseScore 4 or not is beside the point, it's whether you ever installed previous versions, and if so, what customizations you made while testing.
And yes, it's definitely true that lots and lots of improvements have been made in the past year, just check the release notes for the updates over the past year. But, if it's something related to the plugin framework that is forcing you to limit yourself to MU3, unfortunately no real changes there, since it's awaiting a very long overdue more significant redesign.
In reply to Whether you are actively… by Marc Sabatella
(Thanks for the update on the PluginAPI, the MU team remains really vague on this point and has a non-respectful behaviour. Really strange).
About the customization: could customization made in MU3.6 impact MU4.x ?
In reply to (Thanks for the update on… by parkingb
Regarding the plugin framework, not sure what vague information you've seen, but I'm reporting what is public knowledge from the pretty clear and direct statements I've seen here, on Discord, and on GitHub - no special inside information.
As for customization - no, customizations made in MU3 won't ever affect MU4 or vice versa. But remember, even something as simple as adding a palette (like, say, Guitar) counts as customization and causes your workspace to be saved.
In reply to Regarding the plugin… by Marc Sabatella
Ok, in this case. I made a customization. I added a custom Palette. Then, this should be reported as a bug. Because the update to 4.2.0 caused that erroneous palette behaviour.
In reply to Ok, in this case. I made a… by parkingb
Definitely, if you are able to find precise steps to reproduce the problem, it is worth updating the existing bug report that was already filed with those precise steps. Of course, it's about equally likely that the bug was actually in the older version not writing the custom workspace file correctly. And that bug may have been fixed long ago for all we know. But once precise steps to reproduce the problem are found, an investigation can begin.