Hi Norm, I would be glad to try the Beta but I was put off by this text: “don’t use this version for mission critical projects.” How stable is the Beta?
As long as you keep backups of your projects the beta tends to be fine.
The beta also runs along side the normal version of Blocs, so you don’t need to replace your entire workflow.
Just download it, open your project in this version see if its fixed and let me know, if you intend to work with the beta just work with backups of projects incase they become broke (which is very rare).
OK, thanks for your help!
I opened my Blocs file in the Beta Version as instructed. There are still 2 Blocs missing from the Layers navigator.
Could you please send me the blocs project I’ll get it patched up.
I’m using 3.1.2 and am having this problem. I have a navigation bloc that I’ve spent a lot of time on and there’s no way for me to see it in the tree. I want to be able to use the drop down button groups I’ve made but I’m unable to transfer them anywhere else now.
Hi, I have had this problem with build 3, 4 and the current 5.
I think it would be good if there was a tool to do this repair automatically and thus not load @Norm of work.
it’s possible @Norm ??
Afraid not, Im teaching the layer tree to understand the complex layouts that rich text elements like the paragraph can create, it gets messy fast when you are wrapping words in tags etc.
What you have to consider is if it doesn’t load on the layer tree you can always select it on the canvas, I appreciate its not ideal but the problem is not in the file, it is actually the layer tree getting confused and instead of crashing, it simply leaves out what it doesn’t understand.
What would be super helpful is if anyone who is using 3.2 beta and has missing areas, let me know and send me a copy of the file in question with a detailed explainintionm of were the missing sections are so I can patch it up.
Try the beta of 3.2, it may fix the issues. Don’t remake your project, I can issue a patch if required.
I’ve also had some problems with layer tree recently. I msg’d Norm yesterday with a specific problem I had between 3.1.2 and 3.2 beta versions. If possible, it would be nice to have some detect mechanism to let one know that tree had a problem. That way, user could undo problem operation(s) and retry in a different way.
Thanks in advance to Norm for his great ongoing support.
Yes, in the beta of 3.2 things worked for me.
I was able to access at least one of the navigation blocs in the layer tree and this allowed me to extract the drop down button groups I had built and put them into another structure that is working for me.