How do I handel ManipulationDelta Without Code Behind using MVVM?

Question

4.00/5 (1 vote)

See more:

I am building a touch-screen application, and I know I should avoid adding code to the code behind. Which leads to the question of how handle ManipulaitonDelta in the View Model. I have no idea how this can be done, and I am hoping someone can help me out.

Thanks!

Posted 8-Apr-15 12:41pm

Member 10773156

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Fredrik Bornander · Answer 1 · 2015-04-08T20:54:00

Avoiding code behind is not a universal truth that needs to always be applied regardless of context, does it apply in your case?

When people talk about avoiding code behind they usually refer to avoiding putting non UI specific logic into the code behind of a control as this couples the UI to tightly to the rest of the application logic. You don't want the code behind to be aware of and directly modify your business entities (such as a Customer or Order class), in such cases you'll want a view model de-coupling the UI by abstracting the view from the model.

But if you're building something that's a UI control (as I suspect from your question), then it is perfectly Ok in many cases to rely on code behind if the code is something that's tightly bound to the behaviour of the control rather than some application logic.

Consider WPF classes like Button or Grid, these classes aren't backed by view models but still have a lot of code behind because that code is control specific, not application logic specific.

Hope this helps,
Fredrik