Kinect SDK 1.7 InteractionFrame - kinect

I want to know based on kinect for windows SDK 1.7, which have grab function under the InteractionFrame.
Is it possible to only use one hand only eg: right hand only grab?
I had try to make it only 1 hand detect (right hand), but it seems that there is some sort of ghost mouse when i move my left hand.
this is what i had tried:
playerInfo.HandPointers[1].HandEventType == InteractionHandEventType.Grip
but stil there is another pointer merely visible.
thank you very much.

Tlga, I am having major problems setting up the interaction events in my program. Is there anyway you could help me since it seems as though you already have these in place.
I am about to pull my hair out
Ben
Chefbennyj at gmail dot com

Related

Scrolling with wxwidgets

good day,
I have made the scrollbar visible on my panel, but for the life of me I do not know how to capture the scroll events. How is this done? im using versio 2.8.
Even with wxScrolledWindow the scrollbar is visible but how does one get the event and then process it?
I have tried using connect() and no luck.
Pleas point me to an example.
Thanks
Several points:
Using wxScrolledWindow is different from using the individual, standalone, wxScrollBar controls. To capture events for the former, you use wxEVT_SCROLLWIN_XXX events and the corresponding event macros, while for the latter you use wxEVT_SCROLL_XXX.
Typically you should be using wxScrolledWindow which takes care of scrolling automatically, i.e. you rarely need to catch any events, are you sure you really need to do this?
Look at the scroll sample for many examples of using different scrolled windows if you hadn't already.
Do yourself a favour and switch to a supported 3.0 version instead of a decade old 2.8, there is really no reason to start a new project using 2.8 nowadays.

How would you test a mouse? Describing as many test cases as possible?

A question that I have been asked by a professor? Not looking for someone to give me a direct answer but more an idea of how to answer as im quite confused by the Question?
Thanks
Assuming you're talking about the common Computer Pointing Device, not the rodent:
Imagine grabbing a brand new mouse hot off the factory assembly line. You want to test this sample mouse to make sure it functions correctly to the full satisfaction/expectation of whoever's grandma is gonna buy it.
How exactly would you test it? After doing what exactly would you conclude with 100% confidence that "OK, this mouse is perfectly good, no problems at all in any situation!" ?
You might plug it into a computer and see; does it get detected right away? Does it automatically setup the driver? Does it move around well? Does it click well? What if you're using Windows XP? What about Linux? What about inside virtual machines? What about with a USB extension wire? All of these "What If"s are called test cases; cases / situations that you'd want to test for to make sure the mouse works as expected even in that case / situation.
You can also test through..
1) which is the manufacturer company of that mouse
2) Is it required mouse pad ?
3) Is it wired/wireless mouse
4) maximum distance between mouse & device(Wireless mouse)
5) you can also check that "mouse can connect with more than one device same time.."
6) apple's mouse doesn't work in windows device...

wxWidgets, wxCheckBox label sensitive

I'm trying to get wxCheckBox to have sensitive label like it is in some other toolkit's.
It is often too delicate to aim on little box so whole area with label would be much convenient way to change a state.
But I can't find a way to do it.
Any help would be appreciate.
wxWidgets 2.8, Ubuntu 10.04
I can confirm this is a bug in wxWidgets GTK for wxALIGN_RIGHT check-boxes. If we take a quick look at the source code for the wxCheckBox we can see that right aligned controls are created as two seperate parts, a label and a check box and that the label is never connected to to respond to click events. If you create a ticket on the wxWidgets bug tracker then I am sure someone will fix it.

How does "Cinch App" do it?

If you aren't familiar with Cinch, its an application on Mac App Store that allows you to resize ANY window to half/full screen size if you drag the window to the edge of the screen. Exactly like the functionality in windows 7.
Now my question is, how is it done? I have looked all over cocoa apis looking for notifications/delegate methods for whenever a window is being dragged (ALL windows, not just windows owned by the app from which code is running from) but can't find it. Looked in Core Graphics API...Quartz Display Services....but can't find it.
Any help will be greatly appreciated as I have been looking for the past week....Thanks!
Edit: Resize the window is easy since it can be done through applescript bridge..
Are you developer behind i-Snap or some other Mac App Store clone of Cinch?
I'm the developer behind Cinch, and while I try to maintain an "abundance mentality" which basically says "There's enough out there for everyone", I've been upset by the Mac App Store lowering the barrier for entry to this market which has produced a number of half-backed competitors.
I would be thrilled to see some real innovation around the work I have done, and not just clones looking to make a quick buck.
Anyway, you want to look at the Accessibility APIs. It's a Carbon C API. This is probably your best reference: http://developer.apple.com/library/mac/#samplecode/UIElementInspector/Introduction/Intro.html%23//apple_ref/doc/uid/DTS10000728
I've not used the Cinch app, but if I were to do this I'd expect to be using cocoa events. (Also see here) Specifically the mouse handling events, combined with where the mouse is currently on-screen. They probably set a variable when a window is grabbed and then track the mouse pointer until it hits an edge or until they release the mouse button.
Events are very powerful and provide very low level access to what is happening, but can also be very complex. Good luck!
I'm not sure. Maybe the developers combine apple script and carbon events. You can create carbon events to know when the mouse has been clicked or dragged

Tips on debugging UI errors in Windows Phone 7

I have a Windows Phone 7 application and I regularly see "weird" UI glitches that take me AGES to debug. It's a range of issues like controls appearing to have extra margin, scrollbars not appearing, animations looking really glitchy, entire page scrolled down, combobox items offset, etc. etc.
I'm happy to admit it might be me - but how to you debug UI errors like this? I know there's Silverlight Spy for the PC Silverlight Apps. Is there anything like this for Windows Phone 7?
Any debugging tips v much appreciated.
I have found that it is a good idea to start with Windows Phone 7 Design Templates, adopt a version control system right from day one of the project and to edit the XAML, use Expression Blend. The Visual Studio is great for writing code, but, to harness the real power of the tools, Expression Blend is the best to style your application.
HTH,
indyfromoz
Here are some tips:
Many people have issues with the emulator due to their graphics card.
Things like slow animations and ui glitches are very common.
Check that your graphics card is Direct X 10.1 at least and that your Driver
Model is WDDM 1.1
Make sure you have the latest drivers.
Windows 7 has less issues with the emulator than Vista
Make sure you have the latest tools, get the RTM release from the website.
In the RTM release, the frame rate counters are displayed by default in a vertical bar on the left, you should monitor these to check for performance issues
Here are a couple of things which I normally do... none of them are real smart, but sharing nevertheless.
Deploy it after every 2-3 controls that you add and ensure things are correctly laying out.
If by chance it doesn't work the way I am expecting it to, I have a parallel Silverlight 3 project running in which I typically paste the XAML and see if it works fine.
After that, I typically check it out as a Silverlight project since even I am not sure of any tools available for Win Phone 7.
I have favorited this question and I hope someone points us to something more interesting.
There's a lot you can checkout with Blend as Indy suggests. This is really good advice.
Regarding some of your specific issues these aren't necessarily glitches. I'll comment on a couple that stand out.
Extra margin - this and padding are built into the metro controls by design. Again, in blend you can dig into this by retemplating the control and changing properties of objects within the control.
The procedure for this is rclick the control, edit template, edit a copy. Then you can look at the different states and objects and change things as suits. While doing this please keep in mind the App Certification Requirements and UI Design Guidelines.
Regarding scrollbars, these are by design hidden until you start scrolling. You can control their availability with Horizontal/VerticalScrollBarVisibility on relevant controls (or on the ScrollViewer embedded in some controls - again retemplate in blend).
Combobox isn't metro themed so is going to struggle in the fitting in department, but there are posts around where people have done work on this. ListPicker is a better fit imo from the Windows Phone Toolkit released with the RTM tools.
If you can't see any obvious causes for the glitches in your code the first thing I would recommend is to actually test your app on a real device. Somethings - particularly animated objects -don't always look exactly the same when you run them on a device.
I thought I had a animation glitch in one of my apps but it only appears in the emulator. When I run on an actual device I don't see it.
Of course this doesn't help you if you can't get a phone to test it on yet, but before you potentially waste hours trying to debug a problem you might not have I would work on the rest of the app until such time as you can test the app on a real phone.
The same goes for anyone creating animations - don't waste time perfecting animations in the emulator. The timings will almost certainly be different on the actual device, so wait till you have one to test on.