Hi not a programmer but am looking for advice. This is about how touchscreens interact with windows.
In many touch drivers that are provided with touchscreens they come with the ability to set up certain types of mouse mode. For example click on touch, click on release as well as the normal click and drag. I would like to know if there is a way (may be with a registry modification) that will turn the normally supplied windows function of ‘click and drag’ (the bit that draws the blue box on the desktop) into a click on touch that ignores any mouse_move . This will mean I can click on buttons but not drag the cursor around.
Welcome any options.
Kev
Related
I am running a game that has buttons on both sides of the screen, which gives you an easy control on a tablet. But on ARC it makes it difficult to use because you need to move your mouse across the screen a bunch of times. Does ARC Welder have an option to make a key on the keyboard "tap" a certain place on the screen?
If you are comfortable with the concept of scripting, you could use AutoHotKey to use keyboard events to click specific areas of the screen. This would be through your OS, not the ARC, but I think the script can be linked to a specific application so it will only run with that app.
See specifically Click
I am building a Cocoa application that allows you to drag and drop files from a NSTableView to your computer. Personally, and I know I'm not alone, when I use applications like this I grab the files, invoke the "Show Desktop" hotkey which makes all my windows go away and then I drop the files on my Desktop.
However, if the files already exist on my Desktop, or wherever I'm dropping them, an Alert sheet comes up asking if I want to overwrite the files. But since I'm in Mission Control/Exposé "Show Desktop" mode, the sheet is floating in the middle of my Desktop instead of attached to my NSWindow...
Ideally, if my application has to show an alert sheet, while all the windows are offscreen, I would like to bring my window forward and out of this mode so the sheet is attached to it and not floating in the middle of my desktop but I cannot find much information on the subject. I've tried the standard makeKey and orderFront tactics but no dice. I've also looked into NSWindows setCollectionBehavior but none of these options seem applicable unless i just want my window to just always stay out and ignore this mode.
Does anyone know how to bring a NSWindow out of Exposé when in "Show Desktop" mode?
I have taken to participating in mouseless Monday's and Friday's. I have set my windows float and dock tabs to hotkeys that allow me to pull them out or put them back in; however, I want to be able to choose which location to put the tabbed document in. I operate in landscape mode so I regularly have a bottom and a top window in visual studio. I would like to press a hotkey and send the selected document to that part of the diamond guide. Anyone know a plugin or how I can do this?
There's an entire article dedicated to navigating the IDE using just the keyboard, with a section on docking windows and tabs using the diamond guide from the keyboard. So yes, it is possible, and you don't need a plugin for it:
To move and dock tool windows from the keyboard
Navigate to the tool window you intend to move and give it focus.
On the Window menu, click Dockable.
Press ALT + Space and then choose Move.
The docking guide diamond appears.
Use the ARROW keys to move the window to a new location.
The mouse pointer moves with the window as you use the ARROW keys.
When you have reached the new location, use the ARROW keys to move the mouse pointer over the correct portion of the guide diamond.
An outline of the tool window appears in the new docking location.
Press ENTER.
The tool window snaps into place at the new docking location.
Alternatively, you can cheat by simply controlling the mouse pointer with the keyboard, through a nifty system accessibility feature called MouseKeys.
Many mice and keyboards have "zoom" buttons on them. These almost always generate Ctrl+Mouse Wheel messages to the applications, so they are easily accounted for by us programmers.
But my current Logitech mouse has an additional feature. The zoom wheel indeed sends Ctrl+Mouse Wheel messages when scrolled (or, actually, tilted), but when I depress the zoom wheel, most programs restore the zoom level to the default, i.e. 100 %. What kind of message does the mouse send to the application in this case? I cannot find a suitable virtual key code for it.
I should probably say that I have tried to capture this event. In my Delphi application, I wrote handlers for the KeyDown, MouseDown, and MouseWheel events, but non of them are triggered by this mysterious button.
Applications that support this button:
Google Chrome 5.0.375.127
Microsoft Word 2010
Applications that seem not to support this button:
Microsoft WordPad in Windows 7
Microsoft Paint in Windows 7
There is no dedicated shortcut key-stroke or Windows message. Odds are pretty good that the mouse helper has specific awareness of the process that has the focus. And generates the specific command that this program needs to reset the zoom, possibly a WM_COMMAND message. Use a tool like Microsoft's Spy++ to see what messages are generated, if any.
I have a Logitech M570 and downloaded 'set point'.
Not all mice / trackballs have this feature, dead giveaway is having a 'forward / back' button on your mouse or trackball. If you can get 'set point', there are programmable button / wheel options.
find your mouse or trackball on their product page, then, > support > (your mouse), > downloads
If your device can use 'set point', see download button window on the left, insure your Windows version.
Select 'set point'
at the bottom of the window, hit download, go through wizard steps. Download may be fast or take a while.
If it looks like it successfully downloaded, > control panel > mouse. You will see 'mouse properties', look for set point tab.
Try programming 'ctrl' on your 'depress' mouse wheel or 'tilt' button.
I'm a writer, I love my M570 wireless trackball!
Simple question:
How do I detect that the onscreen keyboard has been displayed on windows mobile 7? Is there an event I can add a listener to?
It takes up about half the screen and I want to scroll the view up when it gets displayed...
EDIT:
A comment below indicates more clearly what I'm trying to do: I have a textbox input, and as the user types into it an autocomplete dropdown appears below it (like google suggest). By default, the active control (the textbox) scrolls into view when focussed, and the onscreen keyboard is directly below it. The onscreen keyboard appears in front of my autocomplete dropdown - what I want to do is make the screen scroll a little further up, so there's some room for my dropdown to be shown.
The windows phone UI design guidelines say: "When the keyboard is deployed, the application should scroll to ensure the active edit control and the caret are in view". This happens fine, it's just the non-active dropdown gets hidden behind the onscreen keyboard.
The guidelines also say that an application can choose to show the onscreen keyboard, and can also choose to close it.
At the moment i'm stuck, and I don't think (based on my research and the replies to this question) that it's possible to detect that the onscreen keyboard has been displayed. I'm moving my investigation to see if it's possible to determine the "visible area" of the page (width & height in pixels for example), and combine this with an onfocus for the textbox... not sure if this will prove fruitful though.
Detecting when the virtual keyboard is displayed won't be possible in 7.0, as confirmed by Microsoft's Peter Torr in the WP7 forum on MSDN.
Maybe, as a dirty workaround, you could detect when the position of your text box (or its parent scroll viewer's offset) has changed, as this would indicate that the virtual keyboard has appeared or disappeared.
You can listen to the TextBox.GotFocus and TextBox.LostFocus events to detect when a text box in your application acquires and looses focus.
If an editable element gets focus then the framework will automatically scroll the element into view. So you really shouldn't have to do anything.