enableGesture(); error on Kinect SimpleOpenNI - kinect

everyone. I'm have a problem and i don't no how to solve it. I try to make some tutorials with Hand click on Processing, and always happened the same error, the function enableGesture(); does not exist. What I can do? Can someone Help me?
Thank You

whether it's
kinect.enableGesture();
or
context.enableGesture();
it doesn't matter it just depends on the variable your code chose in this line
SimpleOpenNI 'variable name here' = new SimpleOpenNI(this);
The function enableGesture(); is out of date
All you have to do is change enableGesture(); to startGesture(SimpleOpenNI."gesture");
Where "gesture" can be either
GESTURE_CLICK, GESTURE_HAND_RAISE or GESTURE_WAVE
And it is most likely that you will encounter other out of date functions such as:
enableHands(); which is now enableHand();
addGesture(String); which is now startGesture(SimpleOpenNI."gesture");
removeGesture(String); which is now endGesture(SimpleOpenNI."gesture");
startTrackingHands(PVector); which is now startTrackingHand(PVector);
Hope this Helps
- E.B.

i think this is because of the simpleopenni version you are using. try using
SimpleOpenNI context = new SimpleOpenNI(this);
context.startGesture(SimpleOpenNI.GESTURE_CLICK);
//change constant for other gestures

Related

Set custom timeout to Bluetooth-le write with Quasar-Framework/Capacitor

I'm using the Bluetooth-LE community plugin in a Quasar/Capacitor project.
Since version 1.7.0, we can make timeouts configurable. But how? I need help with the syntax. Can someone give me a fonctionnal example with a custom timeout.
Thank you.
I was also looking for that information. Haven't found any details on the documention but the file 'definitions.d.ts' inside the Bluetooth-LE module.
Try this :
const writeFlag = await BleClient.write(
device.deviceId,
SERV_SYSTEM_SETTINGS,
CHAR_RTC,
dvDateTime,
{timeout:(10000)} // <---- this is what you need
);

In vue3+typescript devtools property does not working

In Vue3+typescript,
Property "devtools" does not existed on type "AppConfig"
But, APIDoc was guide to this.
app.config.devtools = true;
What should I do? T_T
This issue already Handled...
https://github.com/vuejs/vue-devtools/issues/1244

Retrieving exit code in ProcessExit handler?

I'm writing a little C++/CLI application that calls a lot of libraries. Inside some of them there is at least one exit(xyz) and I catch it by handling AppDomain.ProcessExit(). Works fine. Since the call to exit(...) has already been done, I would like to retrieve the exit code passed to this function.
My problem is that it seems that the exit code is not available before the complete exit of the process and, of course, in my handler, the process is not "completely" terminated/exited. For example, I tried:
int ec = System::Diagnostics::Process:GetCurrentProcess()->ExitCode;
But I got an exception. Also it seems that the API Win32 GetExitCodeProcess() will return me a STILL_ACTIVE error??? I hope this value is registered/accessible somewhere?
Any idea? I'm running on Win 7 and Win 10. Thanks in advance for your help.
I have done this using a batch file before.
I create a file called runprogram.cmd(you can create your own name if desired) and place the following in it: -
#echo off
"programname.exe"
echo %errorlevel%
#echo on
pause
replace programname.exe with your exe's name.
double click on the file to run it.
System::Environment::ExitCode;
Process, AppDomain, Environment... I missed this one! I hope my question/answer will help someone some day!

LinkedInApi class with scope

I am trying out LinkedInExampleWithScopes.java example from scribe-java.
However, it errors out on .provider(LinkedInApi.withScopes("foo", "bar", "baz")).
withScopes() is not recognized as part of scribe-1.3.3.jar.
Please advise which scribe-java version is the withScopes() included in.
I had the same problem but 'scibe-1.3.5.jar' works well. Try it.
Download link: http://mvnrepository.com/artifact/org.scribe/scribe/1.3.5

Problem during SQL Bulk Load

we've got a real confusing problem. We're trying to test an SQL Bulk Load using a little app we've written that passes in the datafile XML, the schema, and the SQL database connection string.
It's a very straight-forward app, here's the main part of the code:
SQLXMLBULKLOADLib.SQLXMLBulkLoad4Class objBL = new SQLXMLBULKLOADLib.SQLXMLBulkLoad4Class();
objBL.ConnectionString = "provider=sqloledb;Data Source=SERVER\\SERVER; Database=Main;User Id=Username;Password=password;";
objBL.BulkLoad = true;
objBL.CheckConstraints = true;
objBL.ErrorLogFile = "error.xml";
objBL.KeepIdentity = false;
objBL.Execute("schema.xml", "data.xml");
As you can see, it's very simple but we're getting the following error from the library we're passing this stuff to: Interop.SQLXMLBULKLOADLib.dll.
The message reads:
Failure: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted
We have no idea what's causing it or what it even means.
Before this we first had an error because SQLXML4.0 wasn't installed, so that was easy to fix. Then there was an error because it couldn't connect to the database (wrong connection string) - fixed. Now there's this and we are just baffled.
Thanks for any help. We're really scratching our heads!
I am not familiar with this particular utility (Interop.SQLXMLBULKLOADLib.dll), but have you checked that your XML validates to its schema .xsd file? Perhaps the dll could have issues with loading the xml data file into memory structures if it is invalid?
I try to understand your problem ,but i have more doubt in that,
If u have time try access the below link ,i think it will definitely useful for you
link text
I know I did something that raised this error message once, but (as often happens) the problem ended up having nothing to do with the error message. Not much help, alas.
Some troubleshooting ideas: try to determine the actual SQL command being generated and submitted by the application to SQL Server (SQL Profiler should help here), and run it as "close" to the database as possible--from within SSMS, using SQLCMD, direct BCP call, whatever is appropriate. Detailing all tests you make and the results you get may help.