you will have to do something to force it to rerender to get the changes to show
you will have to do something to force it to rerender to get the changes to show
Toh cool
Tnicee
Tahh okay
Gfor example when i was doing the log stuff
Gi would edit the layout, then make it vertically as short as it could be, then re-expand. boom, most of the log messages had the changes.
There, pressing Ctrl+S is enough to make it hot reload and rerender (that is configurable though, of course; some people don't want it to do that on every save)
Galternatively there's devtools
Gso you can run the app, open devtools, and mess with shit like in a browser's Inspect Element
Tahh neat
Ti hardly ever use flutter's devtools haha
Gyeah i dont use it often either
Tit's nice that it exists, though :D
Tdefinitely super useful
GAvalonia.Diagnostics is pretty sick yeah
Aturns out .net 8 still works on windows 7
A... not very well, but it does
Aeven nativeaot works
Amanaged to get my cli music player working on win7
... just
i had to recompile mixr using mingw just to get it to work, but after that it did, after waiting about 2 minutes for the JIT to compile everything
... just
i had to recompile mixr using mingw just to get it to work, but after that it did, after waiting about 2 minutes for the JIT to compile everything
Athe GUI did not work at all though, failed at glGenerateMipmap
Aalthough since the PC reported that it supports "DirectX 11", i decided to see if my engine runs on it
nativeaot started immediately but of course, failed to create the directx 11 device lol
nativeaot started immediately but of course, failed to create the directx 11 device lol
ANEVERMIND I SPOKE TOO SOON
Ausing llvmpipe through mesa3d
Abut it's a simple UI so the lack of any acceleration is honestly not too bad. and hey, it works
Twooaaaa
Tniiceee hahaha
Aokay it is using 80% of cpu so not exactly recommended lol
Aseems a core 2 does not much like software rendering
Thahaha oh damn
GOh yeah
GImmediate Mode GUIs on a low-core count CPU is gonna be rough
Gunless you intentionally add a 1-2ms wait every render or something
PFWIW GUI applications is why IsEventDriven exists
Pessentially it’ll only render when an event is received or you post an empty event
ASDL WaitEvent also has a timeout option so it can update every, say, half second
Pyep, we haven’t exposed that so far but yeah it’s useful
ACurrently the application just updates using PollEvent but I'm going to move it to WaitEvent
Also will optimize it so that it only updates regions that change
Not sure how easy that will be with ImGui but that's only a "temporary" thing while I create my own UI thing
Also will optimize it so that it only updates regions that change
Not sure how easy that will be with ImGui but that's only a "temporary" thing while I create my own UI thing
AI tried avalonia and while avalonia is great. XAML and anything to do with it is not
AI would use avalonia but yeah XAML and mvvm are stuff id rather avoid
GGi thought i'd hate it all too and i really dont
AIt just seems overly complex for not much gain
AMaybe there's something I'm missing
AI feel like there's a better solution than an MVVM pattern though
Pmaybe, but the separation of UI design from code has always what has made XAML seem so elegant
Pheck it was once so elegant that they had a whole app dedicated to it: Blend for Visual Studio
AI suppose it can be if you can get used to it. Personally I prefer the approach of doing it in code. Which I know avalonia supports, but I'm more for immediate GUIs. If only egui had C bindings...
AMaybe I'm missing something, I'll take another look.
GI do as much as I can in code
GIve said it before but the way I use AXAML/C# is a lot like HTML/JS
Pit’s very hard to do layouts in code is the main problem