PrismLibrary | Prism Library is a collection of PHP classes | Sitemap library

I am working on the same project as OP.

We found about this https://github.com/microsoft/WPF-Samples/tree/master/Input%20and%20Commands/TouchKeyboard. On this sample Microsoft gives some code to fix the issue for WPF with .net framework.

Now this works well for their usecase. But I've been trying to implement their code with a NET 5 project. And to nobody's surprise this does not appear to be possible (the app simply crashes at the starts and overflows)

So does anyone know if there is a way to either make an app work with NET 5 and .net framework at the same time ?

Or

Port Microsoft's fix in Net 5 so we can use it too !

Thx.

So after further re-search I found out how to fix our issue with the help of this post http://mheironimus.blogspot.com/2015/05/adding-touch-keyboard-support-to-wpf.html. and this one https://stackoverflow.com/a/57463543/14620831

how to call it from other modules?

When a service (like the DialogService) is registered with the container, it will be injected into all constructors that request it as dependency if those are resolved from the container.

This works for public MyViewModel( IDialogService dialogService ) { ... } no matter where the code of MyViewModel resides, as long as it's called by the container. No matter where it resides, the view model has to be linked to its view (by naming convention or explicit call) to be found by the view model locator (and thus created "magically" by the framework) or you have to resolve it yourself (e.g. by injecting a Func< MyViewModel> or a hand-coded factory or - do not do this - by injecting the container or - avoid this, too - by calling new and providing the dependencies yourself).

All this works in exactly the same way for view models defined in the main app and those defined in modules.

Navigating via TabbedPages is broken in the latest Prism released version (8.0.0.1909).

[Bug] Navigation when in Tabbed Pages doesn't change currently selected tab #2218

(It seems they finally have fixed this issue but they haven't released a new version until now)

So downgrade Prism.DryIoc to 7.2.0.1422 or wait for the next Prism release...

you use SetBinding to create a binding in code

When you are building a Prism application, your App class should derive from PrismApplication. It sets up all the infrastructure needed by Prism, also the ViewModelLocator that you use. It will automatically wire the current container to the ViewModelLocationProvider to resolve types. That means, any constructor with parameters that was registered to the container would work without any further ado.

However, by default, without any initialization, the ViewModelLocationProvider will use the Activator from the reflection namespace to instantiate types like below, which ulimately requires a parameterless constructor.

I have checked the source code, starting from line 1740 until 1748, it turns out that the very _core._position is the one being updated instead of the GMapControl.Position during MouseWheel Zooming. which means that the UI control itself does not know that the position was been changed apparently.

here's the pull request I have made, hopefully, it gets by the owner. I have just replaced the _core._position to Position.

You should call dialogService.ShowDialog(nameof(NewBatchDialog)); since the name of the view's NewBatchDialog while ShowNewBatchDialog is the name of some unrelated method.

Or you can register the view with a specific name like containerRegistry.RegisterDialog( "ShowNewBatchDialog" );...

For Xamarin.Forms, you can use IValidationRule to do this.

Firstly, creating a class that derives from the IValidationRule interface to are specify Validation rules.

You need to define the d:DataContext for your view. And while you're at it, vote for the feature...