Here is the first beta of Blocs V5.2.0. Lots of new features and of course many more fixes in this release.
Obviously this is beta one so expect bugs and please share ideas on refinements for the new features, especially the new horizontal scrolling container options.
Happy testing and have a great weekend 
Just trying to be helpful and as descriptive as possible 
Yeah there are still areas that need refining, this is one. Also see if you can find a way to edit a locked class I need to make sure that can’t be done.
I just tested the first new feature to export a web page as a screenshot to email and this is what I get:
Did you get the same result with duplicate keyboard shortcut?
Interesting that the image has a scroll bar in the email, does that function?
Also if you use export > image from the main menu is the generated image correct?
No it doesn’t scroll, and if I try, the icon pops up to add markup etc. I can see from the flashing blue cursor on the side of the image that it is full size, just blank below that initial section you saw.
If I export the page as an image it works with the caveat that certain page images are missing for reasons that are not clear.
@Norm Would we be able to customize the Prev/Next Buttons for the Horizontal Scroll Container in the inspector or do we have to manually edit the classes in the CSS?
You can do it with classes I’ll add some info on that next week.
That’s a good point.
This bug is working reliably for me.
As @jerry pointed out, the inspector shows no indication the class could be locked, and while I also think his thought on a different color is a good one I don’t think it goes far enough. Since there are already two different shades used for classes in the inspector, one for freehand and another for regular classes (I’ll call them regular just to differentiate) but the regular classes seems to have a grayed-out shade and the freehand classes have a lighter shade.
It feels to me that the darker shade should be the locked classes and the lighter shade should be the regular classes. The freehand class should be represented with a shade/tone somewhere in between, along with an icon for locked classes and freehand. This in my opinion reinforces the concept without dependency on color. Also, when a user clicks on a locked class in the inspector I don’t see the reason why the class editor needs to popup only to tell the user it’s locked. They would still need to click out and go to the manager to unlock. Seems like unnecessary steps. Why not show them the same option when clicking on a locked class in the canvas?
See image below for reference of a possible solution.
There are a few other things I’d like to point out regarding the class management workflow that I find difficult to work with. It seems a bit disjointed and not very intuitive. I mean once you work yourself through the learning curve you might be ok but it can still be a bit frustrating. I’ll write up something around this in more detain in the next day or so, right now - I’m going to bed. 
At least something 
Great and thanks for the detail here it very helpful.
Considering the previous image I sent, here’s how I see a locked freehand class appearing in the inspector. But of course these are just suggestions based on my interpretation of these use-cases, I’m sure there are other ways to address this. So no offense if it comes across as if I’m calling your baby ugly.
Hey @Norm
Would it be possible to get a custom bric target attribute for a class that the user can add to custom children, sim. to
custom-bric-id-target="true"
Thanks, Bill
Just thought of something else: When a custom bric is updated it’s not picking up any new controls or the related files. Right now you either have to right-click on everything and reset or build from scratch - which is becoming quite time-consuming.
Is there a way on updating a bric, the controls/related files could be updated but keep whatever settings are already set?
Thanks, Bill
Considering we set everything via attributes, I have started adding code that checks for attributes not existing and then updating the HTML based on out of the box defaults for new options when adding something new after launch. Works for me. It’s usually minor on updates.
You can make some changes using .blocs-round-btn in the class editor.
You could over-ride the on-hover for a more customised design. The browser inspector will give you all you need.
.blocs-horizontal-scroll-container:hover .blocs-round-btn
Changing the SVG will require javascript to switch out the SVG markup. Unless Norm adds some additional button styles. 
That would be good if @Norm could do that ! 
