Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 59543 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
Please see the video and see that it is not possible to work with the current workbook.
Version is 1.3-release/8c298a5 on a mac
The sample can be found on github https://github.com/EifelMono/WorkBook/blob/master/Tuples.workbook
I also have a suggestion for a future workbook.
It would be nice to have something like regions in workbooks.
So if you make a demo, you can collapse things you do not need at the moment and later you can expand them.
You can usually adjust your zoom level back and forth to alleviate this issue.
Confirming for now, but I think it's a duplicate of something we already have filed. Will check on Monday.
After changing the zoom level back and forth it works.
But after editing or changing it comes back.
No changes after update of Workbook 1.3.1
See the video
The sample can be found on github
I also have a suggestion for a future workbook and added the to here
* Reset of the current work book (same as close and open)
* Regions around a cell or cells to collapse or expand things during a presentation
* Protected a cell and or a document against changing
* C# Formatting
* Running a Workbook from an url
* Open an Workbook url from a Workbook
* Open folder (with Finder or Explorer) from the current Workbook
Thank you for the suggestions, Andreas. The Xamarin documentation team has also asked for a lot of those features. :-)
You are right, this bug is not fixed in 1.3.1. It's definitely on our radar though.