CHDK UI version 2.0 ? - page 4 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 3 [4] 5 6 7 8 9 ... 55   Go Down

CHDK UI version 2.0 ?

  • 542 Replies
  • 166409 Views
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: CHDK UI version 2.0 ?
« Reply #30 on: 30 / May / 2012, 07:23:18 »
Advertisements
Quote from: philmoz on 30 / May / 2012, 05:06:49
Looking at the current trunk code there does not appear to be any functional difference between the 'Off' and 'Disabled' states that I can fathom.
I think the intent was to have a "normal" mode where overrides worked if they were enabled individually,  a mode where they were all disabled, and a mode where they were all disabled and could not be turned on with the shortcut.

Quote
I suggest we remove the 'Disabled' option state (will also require a fixup in the config file loader) and rename the other states from 'Off' to 'No' and 'On' to 'Yes'.
Probably better to remove the double negative in the wording too ?  Make it :

     Overrides : [ Disabled | Enabled ]
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: CHDK UI version 2.0 ?
« Reply #31 on: 30 / May / 2012, 07:42:12 »
Quote from: waterwingz on 30 / May / 2012, 07:23:18
Quote from: philmoz on 30 / May / 2012, 05:06:49
Looking at the current trunk code there does not appear to be any functional difference between the 'Off' and 'Disabled' states that I can fathom.
I think the intent was to have a "normal" mode where overrides worked if they were enabled individually,  a mode where they were all disabled, and a mode where they were all disabled and could not be turned on with the shortcut.

Ok, makes sense; but I'm not sure how useful that third state really is. Personally I'd still go with getting rid of the 'Disabled' state. A separate option to disable the shortcut button could be added if needed (and could be extended to all the shortcut buttons).

Quote
Quote
I suggest we remove the 'Disabled' option state (will also require a fixup in the config file loader) and rename the other states from 'Off' to 'No' and 'On' to 'Yes'.
Probably better to remove the double negative in the wording too ?  Make it :

     Overrides : [ Disabled | Enabled ]

That would be better; but I was trying to avoid having to update all the language files :)

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)
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: CHDK UI version 2.0 ?
« Reply #32 on: 02 / June / 2012, 00:18:42 »
Suggestion for the CHDK UI.

When entering <ALT> mode display the current key shortcuts, the action linked to them and the current state.

Attached is an example I've coded up - the attached image shows three states of the CHDK UI.
- top image is entering <ALT> mode with normal shortcuts active
- middle is in MF mode on the camera - activates additional shortcuts for Up/Down buttons
- bottom is when the 'Alt +/- debug action' menu item is active

The list is automatically refreshed when the shortcuts are used so the values shown are current.

Potential issues:
- hides a lot of the screen, and is fairly ugly
- if the histogram is enabled it will probably overlap this and will flicker (so histogram should probably be hidden in ALT mode)
- probably needs a config item & menu option to disable the display for users who don't want it

Any comments?

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)
*

Offline reyalp

  • ******
  • 14140
Re: CHDK UI version 2.0 ?
« Reply #33 on: 02 / June / 2012, 01:35:34 »
I think hiding that much of the screen by default in alt mode is not a good thing.

If this was going to always going to display, I'd yave to find some way to make it very compact and unobtrusive. E.g a small icon for the button, and a one  or two word text description for the value, all kept toward the edges of the screen.
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: CHDK UI version 2.0 ?
« Reply #34 on: 02 / June / 2012, 01:39:28 »
Quote from: reyalp on 02 / June / 2012, 01:35:34
I think hiding that much of the screen by default in alt mode is not a good thing.
I'm trying to recall what else we use the rest of the screen for once we are in <ALT> mode ?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: CHDK UI version 2.0 ?
« Reply #35 on: 02 / June / 2012, 01:47:13 »
Quote from: reyalp on 02 / June / 2012, 01:35:34
I think hiding that much of the screen by default in alt mode is not a good thing.

If this was going to always going to display, I'd yave to find some way to make it very compact and unobtrusive. E.g a small icon for the button, and a one  or two word text description for the value, all kept toward the edges of the screen.

Probably; but also a lot harder to implement :)

Been discussing this with waterwingz on IRC.

Current suggestions are to add a 'Shortcuts' menu that allows this display to be enabled/disabled and also to allow the individual shortcuts to be enabled and disabled.

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)
*

Offline reyalp

  • ******
  • 14140
Re: CHDK UI version 2.0 ?
« Reply #36 on: 02 / June / 2012, 01:50:51 »
Quote from: waterwingz on 02 / June / 2012, 01:39:28
Quote from: reyalp on 02 / June / 2012, 01:35:34
I think hiding that much of the screen by default in alt mode is not a good thing.
I'm trying to recall what else we use the rest of the screen for once we are in <ALT> mode ?
Shooting, if you are using a script.

edit: and the focus related shortcuts wouldn't be very useful if you can't see the subject.
« Last Edit: 02 / June / 2012, 01:57:11 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: CHDK UI version 2.0 ?
« Reply #37 on: 02 / June / 2012, 01:51:41 »
Quote from: reyalp on 02 / June / 2012, 01:50:51
Quote from: waterwingz on 02 / June / 2012, 01:39:28
Quote from: reyalp on 02 / June / 2012, 01:35:34
I think hiding that much of the screen by default in alt mode is not a good thing.
I'm trying to recall what else we use the rest of the screen for once we are in <ALT> mode ?
Shooting, if you are using a script.

Disable it once you press the shutter ?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline reyalp

  • ******
  • 14140
Re: CHDK UI version 2.0 ?
« Reply #38 on: 02 / June / 2012, 02:01:52 »
Quote from: waterwingz on 02 / June / 2012, 01:51:41
Disable it once you press the shutter ?
Halfpress maybe. Having to start your script to compose seems undesirable.
Logged
Don't forget what the H stands for.
*

Offline outslider

  • *****
  • 762
Re: CHDK UI version 2.0 ?
« Reply #39 on: 02 / June / 2012, 02:55:24 »
Maybe show it once shutter half press and disable on the second half press. I wouldn't like to see that thing everytime I get to the alt mode. Or made it configurable is an option.

There could be setting in menu:

On entering ALT mode show: [menu | scripts menu | user menu | shortcuts | nothing]
Logged
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick
Pages: 1 2 3 [4] 5 6 7 8 9 ... 55   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal