These are chat archives for AvaloniaUI/Avalonia

5th
Nov 2016
Jeremy Koritzinsky
@jkoritzinsky
Nov 05 2016 01:01
Right... INotifyCollectionChanged works differently and would have to be special cased in each collection.
Johan Larsson
@JohanLarsson
Nov 05 2016 05:57
does Avalonia require INotifyCollectionChanged to be raised on the dispatcher?
Jeremy Koritzinsky
@jkoritzinsky
Nov 05 2016 06:28
It requires anything that changes an AvaloniaProperty to be on the UI thread because the PropertyChanged event is restricted to running on the UI thread.
Johan Larsson
@JohanLarsson
Nov 05 2016 09:10
does that mean inpc must raise on the ui-thread?
danwalmsley
@danwalmsley
Nov 05 2016 09:47
Ok so @jkoritzinsky your work allows my to not worry about dispatching to ui thread for inpc, but not incc?
The I use it to set selecteditem of virtualized list from background thread I get stack overflow
José Manuel Nieto
@SuperJMN
Nov 05 2016 09:57
I've just published the OmniXAML v2 branch in the OmniXAML repo :D
it's like pre-alpha, close to the Big Bang
but it already does a lot of interesting things
first of all, is EASIER to follow and understand
there's no pull parsing, no instructions or protoinstructions, everything in the XAML is read into a syntax tree (I think that's the name!)
José Manuel Nieto
@SuperJMN
Nov 05 2016 10:03
it already uses Markup Extensions, Templates, Namescopes, Content Properties, Converters and property dependencies
I hope somebody could help me porting the tests to xUnit :)
they use MSTest right now
Wiesław Šoltés
@wieslawsoltes
Nov 05 2016 10:51
@grokys @jkoritzinsky Using latest Avalonia build I have found a lot of issues with bindings, see the video https://youtu.be/Ligr97An1h0
Steven Kirk
@grokys
Nov 05 2016 12:41
oh, that's strange, i wonder what could have caused that?
if bindings are fired on the same thread, nothing should have changed...
Jeremy Koritzinsky
@jkoritzinsky
Nov 05 2016 15:16
I don't know why all the bindings got messed up with my PR. Everything seemed to work perfectly fine. I'll take a look.
Also @SuperJMN would you be interested in me adding event support to OmniXAML-v2? I took a quick look at the code and it seemed a lot easier to add attached events than OmniXAML v1 would have been.
Migrate to Netstandard v1.1
danwalmsley
@danwalmsley
Nov 05 2016 17:45
does that mean the wait is over?!
we can fully target netstandard?
Wiesław Šoltés
@wieslawsoltes
Nov 05 2016 17:47
looks like all dependencies are available for netstandard 1.1
Darnell Williams
@Seeker1437
Nov 05 2016 17:50
yoooooo!!!
yaaay!!!
Steven Kirk
@grokys
Nov 05 2016 18:14
the tooling hasn't been updated though, we'd still need two .csproj files afaict
Andrew
@zezba9000
Nov 05 2016 18:34
If I set "Window.Content" to a instance of a UserControl, then change the "Window.Content" to a different UserControl and then back to the original I just see a white background.
Whats the best way to change the UserControl of the window pragmatically?
Steven Kirk
@grokys
Nov 05 2016 18:37
hmm, that shouldn't happen and it's something we do even in the samples
could you create a minimal demo of the problem?
Andrew
@zezba9000
Nov 05 2016 18:39
ya probably
Steven Kirk
@grokys
Nov 05 2016 18:41
thanks i'm (as always) a bit busy right now so if you could create a repro it would really help
Andrew
@zezba9000
Nov 05 2016 19:23
@grokys AvaloniaUI/Avalonia#795
Steven Kirk
@grokys
Nov 05 2016 19:23
Thanks @zezba9000 - I will take a look as soon as possible!