I'm running Phidget21. I'm not ready yet to upgrade to Phidget22. Yes I understand the memory issue. I'm trying to make sure there aren't any memory issues. I suppose I'm curious to know what the proper lifecycle is. On windows it seems executing CPhidget_delete in the detach event is a problem. Whe...

Hi, While porting over to windows from mac, my app was crashing. I isolated the problem to `CPhidget_delete`. I was running the `CPhidget_delete` as clean up on sensor detach event. This was not an issue on mac. This begs the question. When should you run `CPhdiget_delete`? Only on exit? Cheers, Ed

Ok that makes sense. I thought that support for Phidgets21 was going to end.

I still think you need to be clear on what is supported and the recommended way to transition. Otherwise good job with the codebase. It looks way cleaner and more consistent. And the API page is a big improvement

I must have missed something. How do you get a list of attached devices, it was possible with phidgets21 with CPhidgetManager_getAttacheDevices(). I'm using the TemperatureSensors and from what I can tell getAmbientTemperature is now also gone. Or is it a channel now on the sensor? Also https://www....

Hi,

Are there detailed release notes somewhere? I looked around but to no avail. I noticed while upgrading some code `DeviceType` is deprecated? Is there a list somewhere I missed.

Cheers

I'm guessing all the probes I have are ungrounded therefore the 500ms delay is the expected behaviour when the phidget is attached.

I'm going to get myself an grounded probe to confirm. Can anyone else confirm if this is the correct/expected behaviour.

I have the 1048 and the 1051 TemperatureSensors but I noticed something a little strange. I am able to read from the temperature sensors without a problem. However, when I physically detach the sensors and then reattach. The reading taken immediately after the attached event produces very low number...