Disable touch feedback (by code) in windows 8/store apps? - windows-8

Here is what I am talking about:
I know this visual indication is part of the operating system and that it can be disabled in the control panel. However, I would like to know if it is possible to disable this definition in one application.

Thanks to the suggestion provided by Raymond Chen I was able to found the solution for this. Just add this line in your application entry point:
PointerVisualizationSettings.GetForCurrentView().IsContactFeedbackEnabled = false;

Related

openWorldWithSpec making it impossible to return to previous windows

Reading the book "The Spec UI framework". Trying to implement the part described in chapter "Taking over the entire screen".
After executing the code suggested in the book:
WindowExample new openWorldWithSpec
it seems to be impossible to return to previous state. Tried to delete the new WorldMorph in the inspector. Also tried with halos, as the book suggests but those buttons that are available in the halo menu don't allow it to be closed.
Is it an intended behaviour for this (to be executed to prepare an end-user environment and disable programming UI) or am I missing something?
Working in Pharo 5.0, Mac OS X version.
That is indeed intended behaviour, as part of making applications that do not allow access to the development environment anymore. But you can take a look at the code for PharoLauncher to see how you can enable a developer mode
You can actually get back to normal by:
Alt-Ctrl-Clicking on the Morph (macOS combo may be different, this is for Windows).
Clicking on the little wrench and ask for inspect.
In the evaluation pane, do:
self delete
World menu is available again.
Open a browser.
Done.
If one disables halos in settings, this is a tad harder.

Windows 8, Metro app: About dialog box guidelines or suggestions

Are About dialog boxes "dead" in Windows 8 Metro apps? I looked over quite a few apps and screenshots of apps in the Windows store, and did not find any "inspiration".
Is there any guidelines from Microsoft or any article that discusses this issue?
What do you think is the best way to show a dialog box/popup that shows the app name, version, author and a link to the app's home page?
I am thinking of a icon button in the bottom appbar, something like "About Appname", that opens a popup with this information. I am using C# and XAML.
You would place the About into the Settings pane via the Settings Charm using the Setting Contract. You can see the About in almost all of the apps in the Store today. Quick start on adding Settings can be found here: http://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh872190.aspx
Guidelines for app settings here: http://msdn.microsoft.com/en-us/library/windows/apps/hh770544.aspx
Take a look here.
It lets you create dialogs/flyouts very easily from a UserControl. A few lines of boiler plate and you are done. Takes care of animation, UI management etc.

Change the window area in Windows

I have an application (chat) that I am developing for our company (special requirements). We are mostly using WinXP computers. I want it to be topmost and docked to the right, the problem is, I don't want it to overlap other windows that people are working on.
Is there a way to change the default area that other programs can maximize to? Basically, I want it to look something like this:
Is something like this possible? I'm using VB.net so all .net answers are accepted.
Thanks!
Take a look at the following codeproject article:
Application Desktop Toolbars
It seems to do what you require.
This article is about Application Desktop Toolbars, which are
applications that can align to the screen much like the taskbar. The
article will develop a base class for developing such apps.

Adding an item to the system context menu

How do you add an item to the system context menu? I would like to let my users be able to right click anywhere and launch this program. I cannot seem to find it documented anywhere either.
Thanks for your help!
I am coding in vb.net
What you're looking for is creating a Shell Extension Handler for Windows Explorer.
Reference: http://msdn.microsoft.com/en-us/library/bb776881(VS.85).aspx
Unfortunately doing this in a .Net application is a bit of a problem due to the way in which the CLR is loaded for COM plug-in style extensions. Raymond did a great job of exploring this problem here
http://blogs.msdn.com/oldnewthing/archive/2006/12/18/1317290.aspx

Code for extending the NETCF MainMenu to support background color property

I've searched for the solution to change the background color on the Compact Framework's MainMenu control, and the only answer I've found is that you need to create a custom control. Does anyone have example code for this?
I did something vaguely similar where I wanted to handle the WM_EXITMENULOOP message which was not available as an event in .NETCF.
The solution was to "subclass" the Main Menu, an old MFC trick where you replace the WndProc function with your own, handle any windows messages (WM_EXITMENULOOP in my case) and call the base class WndProc for everything else.
Some sample code is available on Alex Yakhnin's blog on how to subclass a control:
Example of subclassing a window in .NETCF
In your case you'd actually be subclassing the Form that the MainMenu resides on, and I think WM_DRAWITEM would be the windows message you'd want to handle yourself.
I haven't tried changing the background color myself so not totally sure this will work, but subclassing would be where I'd start.
There is no way of doing this.
Your right in that you'll probably need to create your own control.
This was something I was considering doing anyway to make the application go on Windows CE and Windows Mobile.
The problem with adding menus when the application needs to work with both is that the menu goes to the top of the screen on Windows CE and covers any controls that might be there.
It would be less hassle in the long run just make a new control.
I tried to do something similar a while back and discovered that you have to write your own menu; essentially from scratch. I gave up because the project I was working on couldn't afford the expense. I also discovered that OpenNETCF has a pretty awesome menu control. I don't know if it's included in their free software, but it might be worth looking into.