Updated images to new docs standard for Windows#7276
Updated images to new docs standard for Windows#7276Jjagg merged 3 commits intoMonoGame:developfrom SimonDarksideJ:dev/image_update
Conversation
Additional tasks: * Update code docs to 3.8 standards * removed any lingering "pipeline" references * Removed redundant pipeline images
|  | ||
|
|
||
| 1. Open the newly created .spritefont file in your text editor of choice, find this line and change it to your selected .ttf font. | ||
| 2. Open the newly created .spritefont file in your text editor of choice, find this line and change it to your selected .ttf font. |
There was a problem hiding this comment.
Please leave this at 1. The markdown renderer automatically sets the right numbers in numbered lists, so conventions often use 1 for all entries in a list so things can be reordered/added/deleted without issue. We should probably have a style guide. I use the MS doc extension for vs code which is great to standardize formatting in md files and detect issues.
You can see the list is correct in the rendered file: https://docs.monogame.net/articles/content/adding_ttf_fonts.html
There was a problem hiding this comment.
Apologies for the delay, sorted now @Jjagg
|  | ||
|
|
||
| You should now see the Pipeline Editor window open up. If it does not open up (you see a text file open), then you can right-click on **Content.mgcb** and select **Open With**, then select **MonoGame Pipeline** in the list, click **Set as Default** and then click **OK**. | ||
| You should now see the MGCB Editor window open up. If it does not open up (you see a text file open), then you can right-click on **Content.mgcb** and select **Open With**, then select **mgcb-editor-wpf** in the list, click **Set as Default** and then click **OK**. |
There was a problem hiding this comment.
Hmm, this is not a very friendly name. I think we should be able to change this, but I don't know how VS picks this.
There was a problem hiding this comment.
You mean mgcb-editor-wpf ?
There was a problem hiding this comment.
Well if you can change it, then that PR should also update the name in the docs, shouldn't affect this PR.
Should be raised as a separate issue if need be (I agree, it's a crap name, seems to be based on the .NET project name maybe?)
There was a problem hiding this comment.
It's the assembly name and the executable name.
There was a problem hiding this comment.
My initial thought when organizing those assemblies was that each platform's executable could be in a subfolder, allowing them all to be named mgcb-editor, but then all supporting assemblies, templates, etc. would have to be duplicated in each platform's subfolder. I couldn't think of a clean way to do this so I just gave them unique names so they could live in the same main folder.
There was a problem hiding this comment.
Yes, we shouldn't change that, just need a way to set the name as it appears in VS. If it's the executable name we can create a shortcut and register that in the Windows registry. Can we reuse the link from the start menu (#7223)?
* Updated images to new docs standard. Additional tasks: * Update code docs to 3.8 standards * removed any lingering "pipeline" references * Removed redundant pipeline images
Updated images to new docs standard for Windows.
Additional tasks: