These are chat archives for AvaloniaUI/Avalonia

1st
Nov 2017
John Stevans
@jstevans
Nov 01 2017 03:41
Hi, I'm trying to work on adding a ToggleGroup control as a fix for AvaloniaUI/Avalonia#224
I've never used WPF and only just learned about Avalonia, so not too sure of the architecture -- I have a small ToggleGroup class, but not sure what type to make it, and also not sure how to hook up a view to it
jstevans/Avalonia@199ad4b
You need to change style selector in your template file
Nikita Tsukanov
@kekekeks
Nov 01 2017 07:15
BTW, I think what you need is SelectingItemsControl
Hm, you are trying to resolve that menu issue...
Not sure that it's the right approach
@grokys take a look
Jurjen Biewenga
@JurjenBiewenga
Nov 01 2017 10:23
@kekekeks Have you had a chance to look at my issue?
Darnell Williams
@Seeker1437
Nov 01 2017 18:41
Can I hook into a d3d9 window with Avalonia?
Nikita Tsukanov
@kekekeks
Nov 01 2017 18:44
If you manage to get a proper synchronization of DX11 and DX9
There will be flicker otherwise
Nikita Tsukanov
@kekekeks
Nov 01 2017 20:31
Meanwhile, Angular 5
And we are too shy to release a "beta"
@grokys
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 20:41
There's a reason I've been pushing us to release faster in the last few months
Nikita Tsukanov
@kekekeks
Nov 01 2017 20:44
Yeah, but things were way too unstable
with deferred rendering and portable.xaml merged in
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 20:52
I agree. Our big upgrades were being added really close to one another.
In the future we can try to focus releases around one or maybe two big features since we've got so many in the upcoming release. That'll let us release more frequently and not have to wait for everything to bake for a while
Nikita Tsukanov
@kekekeks
Nov 01 2017 20:57
The thing is that feature development is kind of... decentralized
I mostly work on platform support stuff, @grokys figures out general layout/binding/rendering
So we'll usually have at least two major change sets
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 20:59
Yeah that is a large part of it
Btw do we have a changelog going for our next release? Or are we going to put that together as the last step like usual?
Nikita Tsukanov
@kekekeks
Nov 01 2017 21:02
like usual
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:02
Sounds about right. It's going to be a really long changelog haha
Nikita Tsukanov
@kekekeks
Nov 01 2017 21:02
Most major changes are:
  • .NET Core 2.0
  • Portable.Xaml
  • Deferred rendering
  • MonoMac backend
plus tons of bugs fixed
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:03
Don't forget the remoting support
Btw I think there might be a small bug in there that I keep forgetting to file. There's a Task.Yield() call that isn't awaited so the rest of the method doesn't move off the UI thread
Nikita Tsukanov
@kekekeks
Nov 01 2017 21:05
Hm
Check if sync context is properly set
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:06
In any case the Task.Yield() call should be awaited. If it isn't, its basically an expensive noop
Nikita Tsukanov
@kekekeks
Nov 01 2017 21:07
It's not even needed there, actually
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:09
We should probably remove it at some point. Some of the analyzers I have installed on my VS instance bug me about it any time I have to build that project.
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:14
Did you see the new API Analyzer the .NET team just released? https://www.nuget.org/packages/Microsoft.DotNet.Analyzers.Compatibility/
It has analyzers for platform compatibility and new a new (non-attribute based) method for deprecation. We might want to start using that if we end up having any issues at some point
Nikita Tsukanov
@kekekeks
Nov 01 2017 21:17
Hm, that's interesting
Do they have a proper analysis for possible NREs?
It takes 5 minutes of the build time to run resharper analysis
Jeremy Koritzinsky
@jkoritzinsky
Nov 01 2017 21:18
I don't think that's part of this analyzer. I think that's being bundled into the c# 8.0 feature