bringing chdkde and chdk back together discussion - page 3 - General Discussion and Assistance - CHDK Forum

bringing chdkde and chdk back together discussion

  • 52 Replies
  • 20841 Views
*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: bringing chdkde and chdk back together discussion
« Reply #20 on: 12 / February / 2012, 04:30:48 »
Advertisements
Is this what happens :  When the camera is in CHDK <ALT> mode and the USB remote is enabled,  activation of the USB power via the remote switch will cause the currently selected script to start running  ? ( i.e.  the same thing happens as would occur if you full-pressed the camera's shutter button at that point) ?

This is the correct description of the remote script start function.

In the current code,  this only works in "Alex Scriptless Remote" mode. If you have the syncable remote mode enabled then you do not see this behavior.  I assume that was for simplicity of coding ?

Yes, many CHDK user have only a DIY remote control.

In the new version,  should this action happen for all remote devices ?Also, should this be a menu-enabled option ?

It would be nice, If any hardware would be useable. A menu option is also a very good idea.

msl
CHDK-DE:  CHDK-DE links

*

Offline rudi

  • ***
  • 126
  • A590IS_101B, SX260HS_100B
Re: bringing chdkde and chdk back together discussion
« Reply #21 on: 18 / February / 2012, 16:24:53 »
Most different /[CAM]/wrappers.c files have one or more bad entries for
Code: [Select]
lens_get_focus_pos()  //valid entry in each stubs.S
lens_get_focus_pos_from_lens()  //valid entry in each stubs.S
lens_get_target_distance()  //for all dry_os equal _GetFocusLensSubjectDistanceFromLens() via wrapper

CHDK-DE Palette 9 for S95 (on CHDK: palette 7; same as sx130) was posted here. What we will do?

CHDK-DE don't use CAM_USE_COLORED_ICONS flag. A solution for dui_draw.c is add this definition on camera.h and set to 1.

rudi

*

Online philmoz

  • *****
  • 3332
    • Photos
Re: bringing chdkde and chdk back together discussion
« Reply #22 on: 19 / February / 2012, 00:51:26 »
Most different /[CAM]/wrappers.c files have one or more bad entries for
Code: [Select]
lens_get_focus_pos()  //valid entry in each stubs.S
lens_get_focus_pos_from_lens()  //valid entry in each stubs.S
lens_get_target_distance()  //for all dry_os equal _GetFocusLensSubjectDistanceFromLens() via wrapper

CHDK-DE Palette 9 for S95 (on CHDK: palette 7; same as sx130) was posted here. What we will do?

CHDK-DE don't use CAM_USE_COLORED_ICONS flag. A solution for dui_draw.c is add this definition on camera.h and set to 1.

rudi

Revision 1680 (release-1.0) and 1681 (trunk) should have the palettes the same now, I've also updated all the wrappers.c files in CHDK to match CHDK-DE.

The CAM_USE_COLORED_ICONS was introduced to CHDK so that it would use the CHDK-DE icons; but only for cameras where it was enabled. My view would be to get rid of this altogether and just use the CHDK-DE icons all the time.

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: bringing chdkde and chdk back together discussion
« Reply #23 on: 19 / February / 2012, 13:15:55 »
It would be nice, If any hardware would be useable. A menu option is also a very good idea.
Done.  Patch file submitted a few minutes ago.

Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline rudi

  • ***
  • 126
  • A590IS_101B, SX260HS_100B
Re: bringing chdkde and chdk back together discussion
« Reply #24 on: 24 / February / 2012, 18:39:47 »
I worked at differences on platform folder.
Attached a patch for chdk. main changes: twice definitions from camera.h, sx200 patch Rev.956, EXMEM for A610_100e

On this files, I don't know what is valid in chdk or chdk-de:
Code: [Select]
ixus100: /sub/100c/boot.c, kbd.c, main.c, platform_camera.h
ixus220: kbd.c, lib.c (JogDail)
s95_100e: boot.c
sx130_101c: movie_rec.c
platform_camera.h: g12, ixus1000, ixus970 (only CAM_HAS_USER_TV_MODES)

Only on ixus40 main folder is a 2nd stubs_auto.S (chdk-de as stubs_manual.S) for kbd.c. Can we change this equal to sx20 (Transfer addresses to stubs_entry_2.S and clean stubs_auto.o on makefile)?

My view would be to get rid of this altogether and just use the CHDK-DE icons all the time.
We would also delete previous icon code?

rudi

*

Online philmoz

  • *****
  • 3332
    • Photos
Re: bringing chdkde and chdk back together discussion
« Reply #25 on: 24 / February / 2012, 21:17:59 »
I worked at differences on platform folder.
Attached a patch for chdk. main changes: twice definitions from camera.h, sx200 patch Rev.956, EXMEM for A610_100e

On this files, I don't know what is valid in chdk or chdk-de:
Code: [Select]
ixus100: /sub/100c/boot.c, kbd.c, main.c, platform_camera.h
ixus220: kbd.c, lib.c (JogDail)
s95_100e: boot.c
sx130_101c: movie_rec.c
platform_camera.h: g12, ixus1000, ixus970 (only CAM_HAS_USER_TV_MODES)

Only on ixus40 main folder is a 2nd stubs_auto.S (chdk-de as stubs_manual.S) for kbd.c. Can we change this equal to sx20 (Transfer addresses to stubs_entry_2.S and clean stubs_auto.o on makefile)?

Thanks for that, I've applied the patch to the CHDK SVN in revision 1695.
I've also cleaned up the stubs entries for the IXUS40.

Quote
My view would be to get rid of this altogether and just use the CHDK-DE icons all the time.
We would also delete previous icon code?

rudi

Yes, that's the plan.

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)

*

Online philmoz

  • *****
  • 3332
    • Photos
Re: bringing chdkde and chdk back together discussion
« Reply #26 on: 25 / February / 2012, 19:39:14 »
Working on the 'conf.c' merging and I've come across a problem that might need some thought.

The config item ID numbers diverge at # 239 between CHDK and CHDK-DE.

These are used when saving and loading the values to the CCHDK.CFG file so changing them will break one groups existing config files.

Any thoughts?

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)

*

Offline reyalp

  • ******
  • 13457
Re: bringing chdkde and chdk back together discussion
« Reply #27 on: 25 / February / 2012, 20:28:27 »
FWIW, I was thinking a while back about making the cfg name release specific, so CHDK 1.1 would use CHDK11.CFG etc.

This would mean that users would need to redo their settings for each release, unless we offered a way to port the previous one. OTOH, it would give us a lot more flexibility to reorganize or clean up between releases.

This sort of thing is why the current CFG is called CCHDK.CFG rather than CHDK.CFG...
Don't forget what the H stands for.


Re: bringing chdkde and chdk back together discussion
« Reply #28 on: 25 / February / 2012, 21:24:37 »
Working on the 'conf.c' merging and I've come across a problem that might need some thought. The config item ID numbers diverge at # 239 between CHDK and CHDK-DE.  These are used when saving and loading the values to the CCHDK.CFG file so changing them will break one groups existing config files.
Any thoughts?
Wipe out (reserve) all the ID's above 239 to the max number currently used by either version.  Start renumbering at the first unused number.  People will lose the settings above 239 (can't be helped) but at least the defaults should be right ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: bringing chdkde and chdk back together discussion
« Reply #29 on: 26 / February / 2012, 12:16:22 »
New question.    Are there any cameras ported to CHDK-DE that are not available in CHDK ?
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics