A better(?) way to control display off

  • 76 Replies
  • 4394 Views
*

Offline reyalp

  • ******
  • 9956
  • Publish
    Re: A better(?) way to control display off
    « Reply #60 on: 24 / October / 2013, 16:05:56 »
    Advertisements
    Can you upload a full dump from the a540 please.
    I only have a short one.
    Posted in the firmware dumps thread.
    Don't forget what the H stands for.

    *

    Offline srsa_4c

    • ******
    • 3135
  • Publish
    Re: A better(?) way to control display off
    « Reply #61 on: 24 / October / 2013, 17:26:25 »
    It would be good to get some testing on VxWorks cameras before committing this to SVN.
    I'll try that. Is there a simple script to test this (I guess it should prove that the method works AND the camera can then continue to work normally)?
    Quote
    Note: the updated finsig_works finds a lot more of the event procs, which also changes some of the existing values - most noticeably GetCurrentAvValue. I checked on a couple of cameras where this value has changed and the new value looks correct.
    Indeed. Someone in the early days identified GetCurrentFocusLensPosition as GetCurrentAvValue, and this was then copied in several ports (including mine)...
    edit: this was actually the old sigfinder's mistake (stubs_entry_2.S was not involved)
    « Last Edit: 25 / October / 2013, 12:12:46 by srsa_4c »

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A better(?) way to control display off
    « Reply #62 on: 24 / October / 2013, 17:30:28 »
    It would be good to get some testing on VxWorks cameras before committing this to SVN.
    I'll try that. Is there a simple script to test this (I guess it should prove that the method works AND the camera can then continue to work normally)?

    Simple Lua script to test display on/off in this post:
    http://chdk.setepontos.com/index.php?topic=10551.msg106514#msg106514

    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)

    *

    Offline srsa_4c

    • ******
    • 3135
  • Publish
    Re: A better(?) way to control display off
    « Reply #63 on: 24 / October / 2013, 18:21:07 »
    updated script:
    Code: [Select]
    --[[
    @title Display On/Off Test
    --]]

    sleep(2000)
    set_lcd_display(0)
    sleep(2000)
    set_lcd_display(1)
    console_redraw()
    Tried the following cams: a410, a460, ixus65_sd630, s80. Works on all, bitmap overlay disappears when the display comes back on (as described in the first post). No other side effects noticed.


    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A better(?) way to control display off
    « Reply #64 on: 24 / October / 2013, 19:21:32 »
    updated script:
    Code: [Select]
    --[[
    @title Display On/Off Test
    --]]

    sleep(2000)
    set_lcd_display(0)
    sleep(2000)
    set_lcd_display(1)
    console_redraw()
    Tried the following cams: a410, a460, ixus65_sd630, s80. Works on all, bitmap overlay disappears when the display comes back on (as described in the first post). No other side effects noticed.

    On my (DryOS) cameras the DISP button cycles through various display modes:
    - display off
    - display on, no bitmap
    - display on, bitmap overlay

    I wonder if it's something like this, where the display comes back on; but the bitmap overlay is off.
    Perhaps calling set_lcd_display(1) twice might re-enable the bitmap.

    No idea if this will work; just a random idea that popped into my head :)

    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)

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A better(?) way to control display off
    « Reply #65 on: 25 / October / 2013, 08:21:17 »
    Added to trunk in revision 3175.

    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)

    *

    Offline reyalp

    • ******
    • 9956
  • Publish
    Re: A better(?) way to control display off
    « Reply #66 on: 25 / October / 2013, 16:19:50 »
    On my (DryOS) cameras the DISP button cycles through various display modes:
    - display off
    - display on, no bitmap
    - display on, bitmap overlay

    I wonder if it's something like this, where the display comes back on; but the bitmap overlay is off.
    Perhaps calling set_lcd_display(1) twice might re-enable the bitmap.
    In my initial testing on a540, I noted

    Quote
    - the bitmap ui overlay (both chdk and canon) may not display after turning on, until you do something that causes the canon firmware to refresh it.
    IIRC the "do something" can be as simple as opening and closing the func menu. Presumably there's an underlying function somewhere that has the same effect, but it didn't seem like a big deal to me.
    Don't forget what the H stands for.

  • Publish
    Re: A better(?) way to control display off
    « Reply #67 on: 29 / October / 2013, 15:08:55 »
    Probably better to maintain the pattern - I'll add it as 'set_lcd_display'.
    At the risk of having everyone run away screaming,  I just have to ask is "set_lcd_display" is redundant? 

    Sort of like saying you got cash from an ATM machine?


  • Publish
    Re: A better(?) way to control display off
    « Reply #68 on: 18 / December / 2013, 18:36:55 »
    It been almost two months,  so I think its safe to suggest / request that set_lcd_display() get added to 1.2.0?

    I know that's not strictly according our release guidelines, but as I continue to update some of the better, camera-agnostic scripts,  it would be nice to swap out the set_backlight() function for this.  Turning off the display is probably the #1 newbie request on this forum after they figure out how to get CHDK running in the first place.

    If philmoz is busy,  I can make a patch pretty quickly.

    *

    Offline philmoz

    • *****
    • 2936
      • Photos
  • Publish
    Re: A better(?) way to control display off
    « Reply #69 on: 19 / December / 2013, 00:59:03 »
    It been almost two months,  so I think its safe to suggest / request that set_lcd_display() get added to 1.2.0?

    I know that's not strictly according our release guidelines, but as I continue to update some of the better, camera-agnostic scripts,  it would be nice to swap out the set_backlight() function for this.  Turning off the display is probably the #1 newbie request on this forum after they figure out how to get CHDK running in the first place.

    If philmoz is busy,  I can make a patch pretty quickly.

    Added in revision 3276.

    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)

     

    Related Topics