CHDK UI version 2.0 ? - page 21 - General Discussion and Assistance - CHDK Forum

CHDK UI version 2.0 ?

  • 542 Replies
  • 98143 Views
Re: CHDK UI version 2.0 ?
« Reply #200 on: 10 / July / 2012, 01:04:43 »
Advertisements
Funny, but after reboot it works. Maybe camera didn't load this string somehow. Nevermind :)
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

Re: CHDK UI version 2.0 ?
« Reply #201 on: 10 / July / 2012, 16:48:05 »
Other problem - when I'm in ALT mode I can change subject distance override using up/down/left/right buttons. But pressing them doesn't remove the help screen so I can't see the override value (help screen covers that up).

Ideally the help screen should disappear always if non-shortcut is pressed - especially true for up/down/left/right as well as zoom.
« Last Edit: 10 / July / 2012, 16:52:04 by outslider »
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

Re: CHDK UI version 2.0 ?
« Reply #202 on: 11 / July / 2012, 06:47:24 »
I create new  tsvstar-uitest branch based on last 1965 revision of philmoz-uitest.
Just to avoid any collision with main uitest branch. I'm happy that chdk go to better ui.

tsvstar-uitest branch contain first discussed by me item (simple mode). I reconcile it to current revision at last.
Other items as I said before exists only as "draft requirements". Could share these docs too.

Purpose of this changes is significant simplification of overrides menu and allow to change values even faster (use jogdial or up-down).


Minor changes:
 - In my opinion "-" as separator name-help is too similar to final "->" sign. Parenthesis have better look.

Major changes:
 - Very short help is displayed on first enter to ALT mode.
   This help will describe how to manipulate by data and expose such important things as incrementors and edit mode (this is for simple mode).
        File CHDK.HLP should exists in A/CHDK/

 - CHDK Settings - Menu Settings - CHDK Mode.
   Toggle between new and old appearance of CHDK. "Advanced" mean "work exactly as before"
   Simple mode mean hide dynamically unneeded right now items and use editmode/quickdisable instead of pairs value-koef. Overrides and AutoISO menus are affected only right now

  When Simple mode is active:
   - press SET to start edit current item (enums are also affected).
    Use JogDial and arrows to change value then.
     press SET again to set new value or DISP to cancel changes.
     Press MENU when in edit mode to toggle off/on current item (some overrides are affected only. this is named "quickdisable").
   - Regular left-right change right from menu is available as before

What was tested and works well on my S95:
- Tv, Av, ISO, Flash overrides

What wasn't tested (have no idea how to test influence of them):
- focus override
- fast_ev_override

What is TODO for this improvement (should be improved in scope of "simple mode"):
- Change Continuous Bracketing items to be in same style simple mode
- Lock iso_koef to 10 in simple mode (this is hidden field for simple mode) and so change label to "ISO override (x10)". may be some kind of ev steps (1/3 or 1/6 step change on left/right)

Known issue:
- Exit from first time guide by MENU cause shutdown. This is unimportant because happens only once.
« Last Edit: 11 / July / 2012, 06:50:50 by tsvstar »

Re: CHDK UI version 2.0 ?
« Reply #203 on: 11 / July / 2012, 10:08:33 »
@reyalp & philmoz :

Before rolling any of these UI changes into the main trunk, this might be a good time to think about making 1.1.0 the stable version, archiving 1.0.0, and starting a new dev 1.2.0 branch ?

My thinking here is that 1.1.0 is fairly stable, has some great new features, is getting the new camera ports almost exclusively, and it's ready to go. 

These UI changes will require a lot of doc changes and wiki cleanup and testing.  Once we start down that path there is no turning back and it's going to take a while to get stable again.  It would be nice to have a new dev tree for this to keep track of which personal changes get rolled in and which are not.

edit : I'd even go so far as to suggest that major UI changes like this should get a major digit rev to 2.0.0
« Last Edit: 11 / July / 2012, 10:11:23 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


Re: CHDK UI version 2.0 ?
« Reply #204 on: 11 / July / 2012, 11:34:53 »
@reyalp & philmoz :

Before rolling any of these UI changes into the main trunk, this might be a good time to think about making 1.1.0 the stable version, archiving 1.0.0, and starting a new dev 1.2.0 branch ?

My thinking here is that 1.1.0 is fairly stable, has some great new features, is getting the new camera ports almost exclusively, and it's ready to go. 

These UI changes will require a lot of doc changes and wiki cleanup and testing.  Once we start down that path there is no turning back and it's going to take a while to get stable again.  It would be nice to have a new dev tree for this to keep track of which personal changes get rolled in and which are not.

edit : I'd even go so far as to suggest that major UI changes like this should get a major digit rev to 2.0.0


I agree. I would only keep 1.2 instead 2.0, but current trunk can be considered as stable IMO.
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: CHDK UI version 2.0 ?
« Reply #205 on: 12 / July / 2012, 04:13:31 »
Other problem - when I'm in ALT mode I can change subject distance override using up/down/left/right buttons. But pressing them doesn't remove the help screen so I can't see the override value (help screen covers that up).

Ideally the help screen should disappear always if non-shortcut is pressed - especially true for up/down/left/right as well as zoom.

But they are shortcuts - there-in lies the dilemma, when should the help screen be removed?

If you recall it originally disappeared when a button was pressed; but you wanted it to remain so you could see when the values changed.

In this case the values aren't shown on the help screen; but are obscured by it.
I can probably get the help screen to hide when these shortcuts are used; but I'm not sure what the best solution is overall.

Phil.

Edit: Revision 1978 has a fix to hide the help screen when the MF adjust buttons are used (it also has all the latest updates from trunk).

« Last Edit: 12 / July / 2012, 04:30:31 by philmoz »
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)

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: CHDK UI version 2.0 ?
« Reply #206 on: 12 / July / 2012, 04:14:52 »
@reyalp & philmoz :

Before rolling any of these UI changes into the main trunk, this might be a good time to think about making 1.1.0 the stable version, archiving 1.0.0, and starting a new dev 1.2.0 branch ?


Fine with me; but will also need to be co-ordinated with the autobuild server so the correct version gets built.

Phil.
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)

Re: CHDK UI version 2.0 ?
« Reply #207 on: 16 / July / 2012, 08:22:32 »
Currently "Bracketing in Continuos Mode" work in matemathical way:
Mode "-" mean deacrease tv96 (make brighter), decrease av96(make brighter), decrease focus value, decrease iso (make darker).

But intuitively "-" should mean "darker" (-Ev), (and also mean shorter exposition not tv96 value)

Any thoughts about this? Maybe change Tv (and Av) bracketing behavior in scope of UI changes?


Re: CHDK UI version 2.0 ?
« Reply #208 on: 16 / July / 2012, 22:05:04 »
final improves of simple mode are posted to tsvstar-uitest - rev1996

* align some lng items (to show that this is subitems, like koef)
* init incrementor for iso and focus with x10
* bracketing menu now have simple mode
* hide OSD "Factor" if it is =1

bracketing and focus overrides was tested for simple mode. work ok

BTW: Are anyone test this improvement or this is unneeded feature?

Personally I start to use chdk overrides, because I'm able to quickly turn on and tune them. Also I'm able to more quick and comfortable tune scripts.

Re: CHDK UI version 2.0 ?
« Reply #209 on: 16 / July / 2012, 23:54:28 »
* init incrementor for iso and focus with x10
I think that I noticed this in a couple of places - very nice.

Can you give me a short summary of the difference between Simple / Newbie / Advanced in the Menu Settings | CHDK Mode ?   (we might want to pick a word other than Newbie btw ...)

Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics