Some possible improvements

[Surrender]

Last time I was thinking about some improvements/changes:
- increase battery progressbar limit to 4200mV (4.2V is overcharge protection) because after battery loading it doesn't show the actual value
- add a option to reconnect after each disconnect without messagebox (windows is known as a packet dropper, see issue #55 for Crazyfly PC Client)
- add a label/textfield or progressbar for the flight duration and a calculated flight time (calcs with average of the throttle and the previous average flight time)
- add time label: if the crazyflie is connected to usb (and is loading the battery) & with crazyradio then try to calc the full load time with mV/s

I have added the first both ideas in the VM and now i don't have to click anything on the computer when i'm 10m away. I also see now the whole battery range from full load to cut-off.

I want to develop this things but i'm overwelmed with bitbucket, clone, fork, branch, tortoisewb, so much repos, ... i don't know how to start and what is what (never worked with bitbucket & other repos-systems).

[smiler]

I want to develop this things but i'm overwelmed with bitbucket, clone, fork, branch, tortoisewb, so much repos, ... i don't know how to start and what is what (never worked with bitbucket & other repos-systems).

There's a lot of info available on bitbucket. I suggest starting out at here.

[Surrender]

I want to develop this things but i'm overwelmed with bitbucket, clone, fork, branch, tortoisewb, so much repos, ... i don't know how to start and what is what (never worked with bitbucket & other repos-systems).

There's a lot of info available on bitbucket. I suggest starting out at here.

Thanks for this tutorial-link! I'll have look onto this page, seems to be very useful (also working with tortoise, except on windows 7).

[smiler]

I want to develop this things but i'm overwelmed with bitbucket, clone, fork, branch, tortoisewb, so much repos, ... i don't know how to start and what is what (never worked with bitbucket & other repos-systems).

There's a lot of info available on bitbucket. I suggest starting out at here.

Thanks for this tutorial-link! I'll have look onto this page, seems to be very useful (also working with tortoise, except on windows 7).

No problem! I look forward to see that auto reconnect code

[Surrender]

Now I'm able to program and commit changes, thanks to your tutorial @ smiler.

In the actual pull request there is the "Auto Reconnect" mode, but it seems to be not accepted by them
Small changes with a big effect that nobody has to press a button when reconnecting. Maybe someone approve my changes.. everybody can check them.

The max. shown battery voltage is also changed from 4000 to 4200mV. No guessing anymore "is it 5V or what?"

My next changes is the flight time calculation (just a average time as reference) & actual flight time label.

[marcus]

Thanks for the code! We just have to quickly test the last pull request and then we will accept it.

[smiler]

I've skimmed through the code but I don't have the possibility to test it right now. However I wonder how it behaves when you turn off the flie. Does it spin uncontrollably or does the client continue to be responsive?

[Surrender]

If you turn out the crazyfly then the pc client is always trying to connect.
There is no "uncontrolable spinning"

Maybe I add a setting form where you can set a timeout value, counter, ...
But for now it just tries to reconnect everytime. If you press disconnect then there is no auto reconnect running, it reconnects only if there was a running connection before.
Eg.g. if someone is searching a crazylfie (flied far away, but still on) then a reconnect should running always.
The pc client does not now if you switched off the CF with a plan or not.