you need to use the .deb version so it has full access to your system.
Ah yeah I am using the snap version
Thanks
Indeed. It's that which forced me to move to a tablelayout managed UI. I had this nicely calibrated design that worked well under all platforms (GTK being then GTK2) and then GTK3 messed it all up with enormous controls. Even now, it's massively wasteful of screen space. I think they ought to be somewhat ashamed. Not every UI calls for touch, after all, and when you end up scrolling to access controls that fit in the UI on every other platform, it just looks terrible to the user (in my experience).
Even with a 4K panel, I end up having to have the tablelayout inside a scrollable to account for this particular 'quirk' of GTK. The horizontal and vertical scrolling is tedious and very saddening when I was deliberately aiming for a UI that didn't have controls out-of-sight and made all of them available without subdialogs, extra windows, etc.
The FastNoise projects are neat - wasn't aware of those before and will be taking a look. The imgui (I guess?) node editor in FastNoise2 makes me still want something like that for Eto :D
The Scrollable now doesn't auto size to the area though :/
i noticed FormattedText has alignment but it seems only horizontal
(even if not, using Measure/MeasureString is a possibility)
for a ListBox, there's no API for that, as I mentioned.
With FormattedText, you can Measure and then align it wherever you want.
though that assumes you're using a Drawable to draw the text.
As far as I'm aware, you could theoretically execute every binary by Eto.Forms on any platform. However the technology used behind the specific Eto platform is the limiting factor. I would say, using something like GDK or OpenTK as your platform should make it executable cross-platform, given the respective dependincies are installed of course.
You cannot create an Eto.Forms application based on WPF or WinForms and execute it on Linux or Mac, as far as I'm aware, since the netcore framework does not support them either, and Eto "merely" relies on both existing technologies to wrap around.
@Auburn you could, theoretically do that, yes. This is how it worked when using .NET Framework or mono. It gets complicated on .NET Core/5+ as you can only compile Wpf or WinForms on windows. I might be able to "fix" that by removing the Microsoft.WindowsDesktop.App framework reference, but I don't know if that'll break other things.
It's either required or not..
Optimizing assemblies for size is not supported for the selected publish configuration. Please ensure that you are publishing a self-contained app.
linux-x64 and win-x64 are fine, and Google isn't giving any helpful answers
It works if I do a self contained binary, but I don't really want that
It's probably whatever the default is
Looks like the default is
copyused