I have the latest version of the MyraUI Editor working.
However, I have to agree with the other poster who is still not finding any actual C# code generated with the export for the controls created.
Another point that should be taken into consideration and should at least be well documented. The properties provided for the grid in terms of the columns and rows are not labeled properly. To define the number of columns and rows the term parts is used such as with ColumnParts. This makes no sense coming from a professional development background. However, since these are existing properties in the API they should at least be provided with some documentation explaining that these properties are used to define the number of columns and rows that the grid will contain.
Again the terms for the properties that are applied to the controls, which determine where they will be placed in the grid are labeled with suffixes as X and Y. Again, from a professional point of view, this indicates pixels\points in a grid coordinate system or an absolute positioning system for controls on a form. Such terms should have been used with the more meaningful term of index. However, since these terms are already in the API, they should be clearly explained in documentation as to how they related to a cell within the grid.
It took me a while of tinkering with the MyraUI Editor to finally understand how these properties work and realize how necessary they are if one is going to set up a complex interface for the game or simulation.
BTW, I meant to ask… The Assets namespace has been dropped in the latest versions of MyraUI. However, objects in my code still require this namespace or a corresponding one.
Which one should be used to replace the Assets namespace?
Myra’s Grid is loosely based on WPF Grid. And latter has similar properties named ColumnDefinitions and RowDefinitions. Though I agree that GridPositionX/GridPositionY should be renamed GridPositionColumn/GridPositionRow. Or maybe even to Column/Row. Or maybe some simple mechanism of attached properties should be implemented. So setting a widget grid position would be same as in WPF:
Could you share exact code that requires Assets?
Older Myra had AssetManager - alternative to the MonoGame Content Pipeline - which allowed to load direct assets. Its usage looks like following:
var texture = _assetManager.Get<Texture2D>("image.png");
You dont need Assets, unless you have above code somewhere.
Sorry for not replying earlier but I have been with other projects in the past few weeks. As to the Assets issue I had asked about…
If I simply comment out the using clause at the top of my “MainGame.cs” class (Game1.cs), the application compiles and runs without any issues. However, if I upgrade to the latest Myra version, the application coughs up a compile issue say that it is missing the Assets library.
I found the exact issue I have been having with the Assets library… Here is the code that is causing the problem…
coBitmapFont = Myra.DefaultAssets.Font;
My Myra General Info Display relies on this font… What is the replacement then???
Myra 0.8.5 is out.
StbTextEditSharp and TextCopy libraries had been integrated in the Myra.
Which resulted in the many new features for the TextField widget(clipboard operations, undo/redo, cursor movements, etc.).
Myra(UI Library for MonoGame, FNA and Xenko) 0.9 is out.
That is another stabilization release without new features, but with many bug fixes.
Also MyraPad had become primary UI design tool: https://youtu.be/NZUCq2RMgZU
Important. Button had been renamed to ImageTextButton.
Myra 0.9.1 is out.
The only new feature is the ellipsis in the TextBlock widget.
Also Myra has two major API changes:
Now texture atlases and stylesheets use xml instead of json. Binary release contains two new utilities to convert old format to new.
Rectangle Desktop.Bounds property had been replaced with Func<Rectangle> Desktop.BoundsFetcher, which is initially set to Func returning the entire screen(Destkop.DefaultBoundsFetcher).
So code like:
_desktop.Bounds = new Rectangle(0, 0, GraphicsDevice.PresentationParameters.BackBufferWidth,
GraphicsDevice.PresentationParameters.BackBufferHeight);
