it takes to much time.14 votes
It would be great if we could export the changes we made in RibbonWorkbench to an XML file and be able to Import these XML files as well.5 votes
This is a great idea and I would like to add it in a future version. Thanks for the feedback!
Hi - unsure if I'm dealing with a solution that is already slightly corrupt in terms of it's ribbons - however I am unable to use the new 2016 version (the one embedded in the toolkit) - to save any changes to ribbons whilst there are warnings present (this didn't affect the old versions) - the warning is just one around the hide actions needing a solution reload so nothing sinister.
I'll head back to the old version for now - the new one seems much snappier :)
Hi Graham – it seems that the new version doesn’t always refresh the messages – could you try clicking the little refresh button on the messages grid – or using the refresh button on the xml tab and see if there are any errors shown in the messages. Thanks!
I can believe you are so arrogant that you enforce the latest update and not allowing our existing installation to work.
It a huge inconvenience and time consuming when I’m trying to get urgent work done.
What world do you live in?1 vote
Make it that when I go to ribbon workbench & a new version is available, I can still use the old version. Frustrating upgrading every time!
I really appreciate the upgrades and improvements, but having to upgrade to the newest version every single time I go to use ribbon workbench is time consuming. I would likely do the upgrade anyway, but not necessarily when I am trying to get something working to a deadline. Thanks for your efforts though. Great tool1 vote
Thanks for the feedback.
The regular forced upgrade was only during the beta phase – now we are at version 1 – there is an optional auto-update that prompts you once upon opening, and allows you to postpone the upgrade until later if you wish.
Is this ok for you?
- Don't see your idea?