CHDK UI version 2.0 ?

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #470 on: 02 / November / 2012, 18:40:30 »

Advertisements

One of the things tsvstar's new menu system tried to do was eliminate the 'Value Factor' component of some of the override/bracketing items.

For example setting the ISO override required setting a value and a multiplier (Value Factor) to get the final ISO override value.

The 'Value Factor' is also used to enable/disable the specific override.

I assume this was coded before the 'increment factor' stuff was added to the menu system (where you can alter the amount that integer values get changed by when you press the left/right buttons). Before 'increment factor' was implemented setting a large integer value would involve many button presses - hence the 'Value Factor' multiplier would be used to make it easier to enter.

Getting rid of the 'Value Factor' stuff is a good idea; but I still think the tsvstar implementation is not ideal (using -1 as the 'off' value and the whole popup dialog bit).

So I've implemented an alternative for review/comments in my philmoz-uitest branch.

This works by combining the on/off state of the override and the current value onto one menu line.
The override value is set using the left/right buttons as before; but now the on/off state of the override is controlled with the 'Set' button (as a toggle).
Also if the value is changed when the override is off the override is turned on at the same time.

A screen shot is attached.

My branch currently implements this for the ISO, Fast Ev Switch, and Flash Power overrides, and the SD and ISO bracketing values.

Internally this uses the same config variables as before; but does change the meaning so the config file saved with this version will not work correctly in 1.1. For example you can set and ISO override of 2000 in this version which is out of range for 1.1 (where you would set 20x100 instead).
I can see two solutions to this:
- change the config file name
- add code to 1.1 to do range checking on the config variables and set them to sane values if needed
I think the second option would be better.

Phil.

OverridesUI.png (9.08 kB, 363x272 - viewed 82 times.)

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #471 on: 02 / November / 2012, 19:10:55 »

Quote from: philmoz on 02 / November / 2012, 18:40:30

So I've implemented an alternative for review/comments in my philmoz-uitest branch.

Thanks for sticking with this philmoz. But I'd also thank tsvstar for his version. Regardless of how we sort this out, both efforts to make things better are appreciated by many of us. If the "best" way was always obvious, we would still be using Windows 3.1.

Saw the svn update to your version .. will download and rebuild this weekend.

Quote

I can see two solutions to this:
- change the config file name
- add code to 1.1 to do range checking on the config variables and set them to sane values if needed
I think the second option would be better.

I'm okay with a new config file when we make a major version change. Its not that big a deal to reset the OSD stuff - which is really all I carry from version to version. Frankly, it makes me comfortable answering user questions and going back and forth from 1.0 to 1.1 knowing there are seperate config files. I know they are supposed to be compatible but when things go strange between 1.1 and 1.2 , the first thing I do is delete the CFG file.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #472 on: 02 / November / 2012, 19:24:38 »

Quote from: waterwingz on 02 / November / 2012, 19:10:55

I'm okay with a new config file when we make a major version change. Its not that big a deal to reset the OSD stuff - which is really all I carry from version to version. Frankly, it makes me comfortable answering user questions and going back and forth from 1.0 to 1.1 knowing there are seperate config files. I know they are supposed to be compatible but when things go strange between 1.1 and 1.2 , the first thing I do is delete the CFG file.

It will probably need a new config version soon anyway to get rid of the hard wired limit on the number of user menu items in the config (and all the problems it would cause if the limit were increased).

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #473 on: 02 / November / 2012, 20:08:47 »

Quote from: philmoz on 02 / November / 2012, 19:24:38

It will probably need a new config version soon anyway to get rid of the hard wired limit on the number of user menu items in the config (and all the problems it would cause if the limit were increased).

To save me the trouble of going back and looking, is that something I did ? I seem to recall looking at it and deciding the existing 14 or so entries was probably enough for anybody. Much like someone else who is now really really rich is (falsely) reported to have said about 640K ....

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #474 on: 02 / November / 2012, 20:47:20 »

Quote from: waterwingz on 02 / November / 2012, 20:08:47

Quote from: philmoz on 02 / November / 2012, 19:24:38
It will probably need a new config version soon anyway to get rid of the hard wired limit on the number of user menu items in the config (and all the problems it would cause if the limit were increased).
To save me the trouble of going back and looking, is that something I did ? I seem to recall looking at it and deciding the existing 14 or so entries was probably enough for anybody. Much like someone else who is now really really rich is (falsely) reported to have said about 640K ....

No, the hard wired user menu item count goes back a long way.
As it is currently implemented changing the limit would be difficult.

Your addition of allowing user menu items to reference scripts adds even more complexity (making it harder to change) - at the same time it makes the possibility of wanting to increase the limit more likely because the user menu is now more powerful.

The ability to store an arbitrary sized list of 'things' in the config file without hard wired limits in the code is needed.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #475 on: 03 / November / 2012, 05:09:08 »

Latest version (2245) in philmoz-uitest has two significant changes.

1. Added a new UI for the Tv (shutter speed) override for review.
2. Re wrote how the user menu data is stored so that the size of the user menu can be altered without breaking everything.

These necessitated a new config file version so this now uses CCHDK3.CFG as the config file.

Some other minor changes:
- re-arranged the 'Extra Operations' menu and adjusted some of the menu text
- changed the Av override to separate the on/off control from the override value (so it aligns with the Tv and ISO overrides)
- fixed some rounding errors in the Tv code in shooting.c when calculating the tv96 value to send to the firmware (e.g. previously if you asked for a 300 second exposure you only got 297 seconds).
- commented out some entries in the language files, some are unused while others will need updating to match the new UI.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12140

Re: CHDK UI version 2.0 ?

« Reply #476 on: 03 / November / 2012, 11:05:53 »

Quote from: philmoz on 03 / November / 2012, 05:09:08

1. Added a new UI for the Tv (shutter speed) override for review.

Played with these changes for 10 minutes. I like - thank you.

I was a bit worried that having double user set-able fields on some menu lines would be confusing. But it was a nice touch to automatically "enable" the override when its value was changed. That made it obvious how it was supposed to work. And it means you can add an override menu line to the user menu using up only a single line of space !

My first instinct when I wanted to disable an override was the "set" button - not sure if that's muscle memory on my part after a little while using CHDK ? Will a new user figure that out too ?

The choice of [ Ev Step / Ling Exp / ShrtExp ] seems to work well - the function is obvious. I like the way you changed the zoom button multipliers to be context sensitive !

One question - why not do the "Override Subj Dist" the same way ? Or maybe I don't understand how that's supposed to work ? Right now it still has a separate Change + / - menu entry (which strangely multiplies by the zoom button multiplier - its mathematically correct but feels strange ?).

Quote

These necessitated a new config file version so this now uses CCHDK3.CFG as the config file.

A couple of other questions while we are in that menu.

1) What does setting the ISO value to "0" do ?
2) Would this be a good time to change the flash override to a string ? ( Off, Low, High ) ?

Logged

Ported : A1200 SD940 G10 Powershot N G16

msl

1280
A720 IS, SX220 HS 1.01a

Re: CHDK UI version 2.0 ?

« Reply #477 on: 03 / November / 2012, 11:28:57 »

Quote from: philmoz on 02 / November / 2012, 07:04:51

Try to do any of these with the new Tv override system (all are possible with the original system):
- a 1/70th second exposure
- a 4.5 second exposure
- a 15 minute exposure
- a 30 minute exposure
- a 1 hour exposure

Those facts speak for you.

Quote from: philmoz on 02 / November / 2012, 18:40:30

So I've implemented an alternative for review/comments in my philmoz-uitest branch.

This works by combining the on/off state of the override and the current value onto one menu line.
The override value is set using the left/right buttons as before; but now the on/off state of the override is controlled with the 'Set' button (as a toggle).
Also if the value is changed when the override is off the override is turned on at the same time.

That's a good idea. I like this one-liner version of the overrides.

Quote from: philmoz on 03 / November / 2012, 05:09:08

Latest version (2245) in philmoz-uitest has two significant changes.

1. Added a new UI for the Tv (shutter speed) override for review.
2. Re wrote how the user menu data is stored so that the size of the user menu can be altered without breaking everything.

These necessitated a new config file version so this now uses CCHDK3.CFG as the config file.

Some other minor changes...

This new Tv override UI is on a very good way. I like it. I see only one minor issue. The long exposure time is also available for cameras without extended exposure time (tested with the A720). I think for such cameras is the menu option 'long exposure time' not necessary.

A nice detail is the input for h:mm:ss *thumbs Up*

Need we really the multiplier for subject distance input? An on/off toggle as for the other overrides would be nice.

Thanks for all this improvements. With this is CHDK on a good way. tsvstar's version was a good start point for the new UI. Also thanks for that.

msl

Logged

CHDK-DE: CHDK-DE links

philmoz

3450

Re: CHDK UI version 2.0 ?

« Reply #478 on: 03 / November / 2012, 16:32:13 »

Quote from: waterwingz on 03 / November / 2012, 11:05:53

Quote from: philmoz on 03 / November / 2012, 05:09:08
1. Added a new UI for the Tv (shutter speed) override for review.
One question - why not do the "Override Subj Dist" the same way ? Or maybe I don't understand how that's supposed to work ? Right now it still has a separate Change + / - menu entry (which strangely multiplies by the zoom button multiplier - its mathematically correct but feels strange ?).

I'm still thinking about how to deal with this one - the complication is that you can change the SD value directly in ALT mode without going into the menu (on some cameras at least).

If you are in MF and enter ALT mode then two lines are displayed at the top 'SD:' and 'FACTOR:' with the current override and adjustment values. You can use the button/jogdial to adjust the SD value and the zoom to adjust the FACTOR value.

This is why FACTOR (what I renamed to 'Change +/-' in the menu) is used the way it is rather than being a multiplier.

The other complication is that the SD value on some cameras can go up to 9 million so the menu increment amount needs to extend to higher values.

Quote

Quote
These necessitated a new config file version so this now uses CCHDK3.CFG as the config file.

A couple of other questions while we are in that menu.

1) What does setting the ISO value to "0" do ?
2) Would this be a good time to change the flash override to a string ? ( Off, Low, High ) ?

An ISO of 0 sets ISO to AUTO on my cameras.

The flash power strings is a good idea, I'll look at that.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

dvip

451

Re: CHDK UI version 2.0 ?

« Reply #479 on: 04 / November / 2012, 11:24:16 »

Got philmoz-uitest@2247 running in both the sx40hs/a590is, it is working fine. I like the new "Ev Step Value" UI, since it takes less screen space.

>You can use the button/jogdial to adjust the SD value and the zoom to adjust the FACTOR value.

I like this.

Have you noticed any difference (sx40) between iso 20 and iso 100?

Logged