Derek Antrican

Looks like I'm seeing the lightbulb & quick fixes on `Ctrl+.` now that I have added the using but they go away if I remove it. Weird - guess it...

I've found the OmniSharp exception info in the logs and cleaned it up a bit: ``` System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions...

What do you mean by "analyzers packages"? I just installed the OmniSharp/C# extension into VS code from the marketplace. I don't know anything about Roslyn

`CFBundleShortVersionString` for one. Also the README is just generally lacking a lot of info. Running `dotnet msbuild -t:BundleApp -p:RuntimeIdentifier=osx-x64` (as per the README) for the first time and I got...

+1 - could really use a "Ctrl+Y" redo function

I found the workaround for `DisplayMemberPath` using something like: Is there a similar workaround for `SelectedValuePath`?

I think I ended up doing what @maxkatz6 suggested and creating another property in the viewmodel

Thanks for the analysis. It sounds like the assumption is that the same distance you retract at the beginning of the pause, should also be the same distance extruded after...

I was also able to reproduce this very simply by just this code (Avalonia 0.10.0, .NET 5): ```xml Item1 Item2 Item3 Item4 Item5 Item6 Item7 Item8 Item9 Item10 Item11 Item12...

First off - thanks for the PR, but I doubt it'll be merged in. But, can you explain this a bit more? This is the first time I've ever seen...