I'm starting to get really confused by the different ways to recognizer text. Some are ancient and some are for Windows Forms or WPF ...
Today, if I only need to traget Windows 10 what Ink technology should I use?
I've been trying to use InkCanvas and all the docs talk about InkPresenter.
However InkPresenter is not a member of InkCanvas ...
InkPresenter
Any ideas please?
InkCanvas is a WPF control and InkPresenter is a UWP control. Which one to use depends on what kind of application you are developing.
These are different kind of applications. A classic WPF desktop application runs on all Windows PCs including Windows 10 machines while Universal Windows Platforms (UWP) apps have the potential of running across all Windows 10 devices including phones, HoloLens and XBox: https://learn.microsoft.com/en-us/windows/uwp/get-started/universal-application-platform-guide.
Related
For some reason everything I've found online says that the Accelerometer class is only for winRT applications and I can't use it unless I code against winRT. I dont understand what winRT is. And my app can't be a metro style app because I need special access to different APIs that I've read can only be accessed in a WPF app. Also windows 8 metro style apps wont work with windows 7 which I would like my app to work for. Also I've only recently started programming so explain it to me like I'm a 4 year old.
Thanks!
The accelerometer you are referring to is a specific WinRT (Windows RunTime) class which is not available in .NET.
WinRT API was made for phones and tablets, but also integrated in Windows 8 / 8.1. It's basically the API for 'Metro' apps and therefore requires such an app. It will definitely not work for Windows 7, since WinRT is not available for this OS. I'm also somehow wondering, why you would need an accelerometer on Win7 (Notebook?), but that is a different topic.
I've once tried to get WinRT stuff working in C#.NET, and to my knowledge, this is not possible.
If you can provide us any additional information about your idea, maybe we can offer you an acceptable alternative.
I have two simple questions since I'm very new to Windows Phone programming:
1:
How do I cange the root frame, or show a different Page on startup, in a Windows Phone 8.1 Silverlight application? I have a LoginPage and then I want to check if the user is logged in show MainPage as root frame and if the user is not logged in show the LoginPage.
2:
Windows Phone Silverlight applications seems so different to me compared to the Windows Phone WinRT applications, or maybe I'm just not experienced enough. For example I can't put a placeholder/hint text in a textBox in Silverlight but it's super easy in WinRT, why is it like that? Isn't that something very basic that many IDE's implements? Or have I missed something mayor when I'm developing a Silverlight application for Windows Phone?
I know that Windows Phone WinRT is used to create universal apps and Silverlight is used to create only mobile apps for Windows Phone, but why is developing a mobile app in Silverlight so much different (at least to me) compared to build a Windows Phone app i WinRT?
For your first question, use the UriMapper.
The basic principle is that you check if the user is logged in or not and based on that, navigate to the correct view.
The code is not all that complicated, there is a very good tutorial up on Shawn Kendrot his blog here...
For question 2, how to add some sort of hint/watermark can be done in several different ways.
But a very simple version is presented on MSDN here... it uses events to set and clear the watermark.
Point 1
You have to go to Package.appxmanifest and under the tab called Application the second field contains the startup page name. Currently it should be MainPage.xaml, just change it to LoginPage.xaml.
Point 2
I don't quite understand your question. Silverlight and Windows Runtime are two different platforms, they have in fact many different libraries. The goal of Windows Runtime is to run the same application on several different devices, so different hardware requirements and different resolutions. It was a need to organize the environment differently and of course Microsoft added some minor changes such as the hint text (e.g.).
What is so different to you? I did the porting of an app from SL to WinRT but it's not difficult nor tricky at all.
Is there any future of winform and wpf app in smart phone or tablet market. will we be able to develop applications for window store on winform or wpf. Or are they a dead technology
Thanks
I don't think they will be dead so soon. may be yes for Winforms. but still there are tons of applications that are running on Winforms and even on consoles.
you can use XAML for smart phones as well as tables. even WinRT supports XAML. also there are new libraries out there you can write programs targeting multiple platforms such as Portable Class Library
The new standard for building desktop applications is WPF. This is currently not deprecated and will not be for the foreseeable future. When developing for Windows phones and tablets there is an API very similar to WPF in structure/feel (using XAML).
I 'am developing an app targeted to WP7.1 but I want it to work well on WP8 devices too. Assuming creating layout using dynamic resizng elements (grids with auto height etc) will the app scale just like WP8 app under Windows Phone 8 (WP8 handles WVGA HD WXGA resolutions)? If yes, is this possible to get a exact screen size under WP7 and what about in-app images in high resolution? If not, should I build 2 different apps to handle scaling well? One for WP7 and another for WP8 (even if the only change is build target?)
WP7 only supports 800x480 resolution and will automatically scale on WP8.
WP7 app cannot however do any resolution dependant tweaks when app runs on WP8. You need to recompile it to WP8
How to approach a modern GUI development in Windows Mobile 6.5. I can see in .NET CF 2.0/3.5 only legacy common controls, no alpha blended controls, no fading etc. Comparing to Android or Symbian, Windows Mobile 6.5 look-a-like of applications is very elderly.
Is there support for WPF in Windows Mobile 6.5?
Thanks and Regards
Dominik
WPF is not supported. Silverlight is not supported in current phones but will be supported with Windows Phone 7. XNA will be supported on Windows Phone 7.
For the current phones on the market you really have to abandon the idea that you're going to get a decent UI by simply dragging controls out of the toolbox. That simply is not going to happen. You can still create compelling UI, but you have to do custom/manual drawing of your controls.
Never heard of WPF development for WM.
But there is Silverlight 4 and (theoretically) Windows Phone 7... So if you want to develop for Windows platform you'd probably target Silverlight technology, not WPF. And Windows Phone 7, not WM 6.5