Blumentals Software Community

Aivars wrote:No more crash?

Installed without problems
No errors on startup

I did not actually work with the new build yet, but it looks fine.

Yes, that worked.
Thanks

Nope

This is, what I get on install:
http://s8.postimg.org/whodq5out/webuilder2016.png

I cancelled the installation, rollback did not work correctly and left me with a corrupt, and not working installation.
Once again, build 800 to the rescue and it works again.

Hi again, I just installed the latest build 181 of WeBuilder 2016. 180 was working fine before. The new version gives me an error message *every* time at startup. I tried sending the report from there, but it did not work. When I click "continue with application", it starts and looks normal. But ...

Thank you Aivars,

I never noticed the Export Settings function before.
And just in case, I backed them up right away.

Hi, I upgraded from WeBuilder 2014 to 2016. To my great joy, all my snippets and all my projects were perfectly imported. A few minor changes to the layout and I was ready to go. Great job here! Now I have "WeBuilder 2014" and a "WeBuilder 2016" folder in Programs. Is it safe to deinstall the 2014 ...

Hi everybody, I was still using WeBuilder 2014, since 2015 did not have any features that I absolutely needed. Yesterday, I received the mail about the new version. Which I bought immediately. Why? Because it finally, finally has my single most wanted feature: The X for closing tabs. This may sound ...

Thank you, thats fantastic! I already had tried dragging the icons with STRG, ALT and SHIFT pressed, but I would never have thought of this trick ;-) 1st problem solved. Middle-clicking the Tabs works too and I could get used to that, but maybe you could make individual close-buttons an option in a ...

Hi, I love WeBuilder, but two rather small things bother me and I was wondering if these can be changed: 1) I'd like to rearrange the order of the icons in the Standard-Toolbar, but I find no way to do so? I even tried to manually edit the "Default.lay"-file, but it seems to make no difference, even ...