was wondering if I can help testing some things.i have firmware and automatic update functioning.
so i tested that first by using a script that support zoom and that froze the camera.
I was going to say why would you want to use a zoom script on this camera, but then I realized that the set_zoom() script command did indeed crash the cam. So, thanks for reporting that. Should be fixed in revision 5147.
in my opinion disabling a function is better than crashing the camera by mistake..
the second thing i can report, but maybe that should be in the screen flicker menu thread.I noticed that scripts that use an osd (white box with blue header) the height is not right making it hard to read (text lines overlap), and with most camera's i own that box is in the top middle of the screen, while here it is top left, see picture
That's an issue that affects all D6 ports: these have (by our choice) higher resolution screens AND a larger default font. AFAIK scripts can't easily know when they run on one of those cameras, and they all use hardcoded coordinates and font sizes.
hereby the UI script i adapted and has an extra flag at the bottom in the menu for doubling height. (sorry Waterwingz for this crude hack into your clean code)
Having said that, we need to add a way to detect & handle this script side (assuming there is really no way to do this today).
QuoteHaving said that, we need to add a way to detect & handle this script side (assuming there is really no way to do this today).maybe a separate functionfile you can call that adds x2 to line height and doubles space from the left to the osd if triggered by screen resolution. what i notice is that screen flicker is a lot less with this so
Traveling now so don't have time to search but I'm very sure we have been down this path before.
Started by axman
« 1 2 3 »
Started by burglar
Creative Uses of CHDK
Started by reyalp
Started by David475