 TheXamlGuy
|
99855e77b9
|
Popup had a fake invisible padding around it... however it seems we can now use the window now anyway
|
2024-01-16 08:15:57 +00:00 |
|
|
TheXamlGuy
|
1283e8ff58
|
Too much to name... but damn, it got where we are needed
|
2024-01-14 15:06:30 +00:00 |
|
|
TheXamlGuy
|
2a773f26db
|
Wire up the disposer for cleaning up unused objects, i.e disposing a VM will remove it from the view
|
2024-01-12 21:05:42 +00:00 |
|
|
TheXamlGuy
|
d7d90b3d54
|
wrapped custom widget items in containers so we have more control of the surrounding, i.e. divider
|
2024-01-10 19:25:16 +00:00 |
|
|
TheXamlGuy
|
66f65185c8
|
Fixed
|
2024-01-06 18:15:20 +00:00 |
|
|
TheXamlGuy
|
9fdb125c13
|
restructure
|
2024-01-06 16:56:32 +00:00 |
|
|
TheXamlGuy
|
71881ad877
|
wired up key commands
|
2024-01-06 16:39:30 +00:00 |
|
|
TheXamlGuy
|
53537aa4c7
|
Added messaging pipeline
|
2024-01-06 13:57:18 +00:00 |
|
|
TheXamlGuy
|
4a27534e39
|
Make custom widgets independent of any WinUI framework concerns. Although one can add WinUI concerns to ther widget if they want to build a fully customized widget. In theory, it may also be possible to host a widget of WPF, Avalonia, or Blazor.
|
2024-01-06 09:57:23 +00:00 |
|
|
TheXamlGuy
|
3e88950669
|
Rename projects to better structure it. The aim is to try and keep it not dependant on the type of UI framework it uses thus allowing us to switch to another UI framework if we need later...
|
2024-01-06 08:49:12 +00:00 |
|