Not quite right, but I’ll take guesses from a few more people before revealing the secret.
BTW I’m counting all lines of code including the code for splitters and resizing. Any changes to settings in the IDE/design time are not counted as code.
Edit:
I must say I was quite please with the results myself.
No clue about how many lines of code this might be, but I am really curious to learn HOW you achieved this. I really would like to peak into this code!
Wow.
This evokes fond memories of building apps with Delphi, where controls could be ‘locked to parent’ and no user-written code was needed to do this at all.
[quote=352849:@Christoph De Vocht]That looks sweet!
My guess or wish is that you are using a non-public beta build of the next Xojo version. :-)[/quote]
That’s exactly what WPF does. And can be verified using a tool like Window Spy from AutoHotKey.
Doing that in Xojo with a canvas would defeat the purpose of using Xojo and would esentially be re-inventing the wheel.
[quote=344335:@Michel Bujardet]… I have developed that kind of interface for my own use, precisely because native controls are so, so tired.
Maybe our basic misunderstanding is that you refuse to put in the work yourself, and want a ready made solution…[/quote]
[quote=344221:@Cho Sing Kum]The Modern Windows UI is not based on .NET. They are XAML controls. The use of C# or VB(.NET) and also C++ and JavaScript is only for the code behind the controls. The use of .NET controls will result in a WindowsForm app which is still Desktop app.
Xojo can implement XAML controls and use the Xojo language to code behind. Or they implement their own equivalent of XAML-based controls.[/quote]
It doesn’t make sense to me for each developer to create his own equivalent of XAML for himself. This is 2017!
I’m not sure about that, I’ve been considering starting a project that does exactly that when Xojo release its Xojo-developed plugin solution. But I’ll wait to comment or pass judgement until I’ve seen the windows framework updates that are coming.