I recently updated my 3.6 dev build of Monogame with the latest snapshot build and noticed that the pipeline tool UI has changed quite a bit.
Anyone else having issues with the UI not updating correctly (and not being able to scroll to the bottom)?
The bottom of the tool UI seems to extend below the windows taskbar so I can never tell when the tool is complete. I have to constantly resize and then maximise it in order to see the last couple lines to determine if it’s complete or not.
I think I know what you mean, this is with the window filling the screen right?
It happens from time to time, I just make it a small window and then drag the base border all the way to the bottom and then the same with one of the sides, same works for top drag…
Yes, it’s when the window is filling the screen. I can get it to kinda work by fiddling around with the UI as you mentioned, but it’s pretty annoying. I’ts also time consuming when I am debugging a content pipeline extension I am working on and have to constantly close the UI and re-open it after I change my pipeline code (since the DLL is locked when the tool is open).
I am not sure why the UI was changed… the previous UI worked fine. Hopefully these issues will get fixed before the final 3.6 is released.
The UI is changed because we changed the GUI library used so we can maintain the same code base for both Windows and Unix. Before we had separate codes for Windows Forms and Gtk, while now we are using Eto Forms.
@harry-cpp Thanks for the details on why we changed the UI. I think it’s definitely a step forward and I am sure I will feel a lot more enthusiastic once the glitches are fixed I like how much faster it is now.
I posted 2 screenshots showing the bottom of the tool when I run it. As you can see, the scrollbar (on the right) is not there / visible, and the bottom of the tool extends below the windows taskbar, so you can’t see what’s going on, and you can’t scroll (since there is no scrollbar).
I am running a dual monitor setup, with my primary monitor being 4k. I am not sure if that has anything to do with it.
I’ve also seen some other minor glitches like the tool showing as being completed i.e. says succeeded, but a couple of the asset icons still show as busy i.e. clock icon.
@harry-cpp I have never worked with Eto or done any CSharp UI / form based stuff, but I have done a fair amount of form based stuff using Java (Swing / JavaFX)… so I am not sure if this will help…
In Java you can set the scrollbar policy to Show Always vs Show as Needed. I am wondering if that might fix the problem. Although, it sounds like the issue might be that events related to the scrollpane / listpane are not being triggered appropriately when more items are being added to the list.
On a slightly different note. Is there a way to capture / display the logging information (using the Content.Logger) that is sent from the pipeline processors? I am only able to view that information in Visual Studio by running my project.
It would be nice if there was an option in the pipeline tool to capture / view that. Or maybe it’s already there and I am missing something?
Thanks for all the work you’re doing to improve the tool!