1.3 development planning thread - page 2 - General Discussion and Assistance - CHDK Forum

1.3 development planning thread

  • 43 Replies
  • 12781 Views
*

Offline philmoz

  • *****
  • 3128
    • Photos
Re: 1.3 development planning thred
« Reply #10 on: 02 / August / 2013, 19:32:21 »
Advertisements
3 files as proposed in phils final post might be a good compromise, I'm not totally against it.

Started looking at this and I think it should be done together with this:
* Lua library to access to conf settings by name (split conf defines into an include, generate table like propcase and modemap) http://chdk.setepontos.com/index.php?topic=9602.msg98965#msg98965

The easiest way to implement the config split is to create new ConfInfo structures in conf.c - the code is already set up with functions to read/write this struct to a file.

I'm also thinking that each ConfInfo should generate a seperate Lua library file so you only need to load the one whose settings you want to access (otherwise the Lua library file will get large).

Finally is it worth putting the GPS settings in their own config / library file? There are very few cameras with GPS so removing these from the general Lua library makes sense to me.

Phil.

Edit: Patch posted here http://chdk.setepontos.com/index.php?topic=9602.msg103557#msg103557
« Last Edit: 03 / August / 2013, 22:10:23 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)

Re: 1.3 development planning thred
« Reply #11 on: 03 / August / 2013, 00:09:27 »
A couple of things I've been thinking about - most have been discussed before.

1) User customizability : 
 - CCHDK2.CFG broken out so that OSD setup is stored seperately
 - allow the person doing the port to specifiy the default OSD layout for that port

2) Scripting Enhancements
 - allow scripts to be activated from the User Menu (in addition to script loading currently supported)
 - allow certain events to launch a unique script ( power up, Scene mode selected, shooting, shortcut button pressed ..)
edit :

3) User Menu
 - allow scripts to be activated from the User Menu (in addition to script loading currently supported)
 - allow seperate CHDK configurations to be stored & named (somehow) and then to be loadable from the User Menu by name

4) Background Task
 - allow one specific script to run in the background while not in <ALT> mode (this kinda works now I think but behavior is not guaranteed and there is no way to make it automatic).
« Last Edit: 03 / August / 2013, 00:13:57 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: 1.3 development planning thred
« Reply #12 on: 03 / August / 2013, 22:54:03 »
2) Scripting Enhancements
 - allow certain events to launch a unique script ( power up, Scene mode selected, shooting, shortcut button pressed ..)
- allow parameter sets to be named rather than simply numbered.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: 1.3 development planning thred
« Reply #13 on: 04 / August / 2013, 17:56:29 »
A couple of things I've been thinking about - most have been discussed before.

1) User customizability : 
 - CCHDK2.CFG broken out so that OSD setup is stored seperately
 - allow the person doing the port to specifiy the default OSD layout for that port

2) Scripting Enhancements
 - allow certain events to launch a unique script ( power up, Scene mode selected, shooting, shortcut button pressed ..)
- allow parameter sets to be named rather than simply numbered.

3) User Menu
 - allow scripts to be activated from the User Menu (in addition to script loading currently supported)
 - allow seperate CHDK configurations to be stored & named (somehow) and then to be loadable from the User Menu by name

4) Background Task
 - allow one specific script to run in the background while not in <ALT> mode (this kinda works now I think but behavior is not guaranteed and there is no way to make it automatic).

5) High Speed Sync
- provide support for vnd's high speed sync mod in sigfinder (if possible) and as a #defined build option in platform_camera.h .  This should help with the mulit-camera "bullet time" rigs that people are using with CHDK

6) Lapser's continuous shooting mods.

« Last Edit: 06 / August / 2013, 20:41:57 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Online reyalp

  • ******
  • 12145
Re: 1.3 development planning thread
« Reply #14 on: 06 / August / 2013, 00:31:15 »
Don't forget what the H stands for.

*

Online reyalp

  • ******
  • 12145
Re: 1.3 development planning thread
« Reply #15 on: 24 / August / 2013, 14:55:19 »
Exposure / apex function discussion split to http://chdk.setepontos.com/index.php?topic=10584.msg103918#msg103918

Some more a 1.3 item:
Allowing scripts to trap full & half press shutter button activations
http://chdk.setepontos.com/index.php?topic=10580.0

Let scripts figure out what keys exist:
http://chdk.setepontos.com/index.php?topic=9722.msg104397#msg104397

Let scripts hook into the shooting process:
http://chdk.setepontos.com/index.php?topic=9722.msg104397#msg104397
Don't forget what the H stands for.

Re: 1.3 development planning thread
« Reply #16 on: 24 / August / 2013, 15:13:49 »
When did the CHDK/LUALIB/GEN/cnf_core.lua  stuff slip in there ?

http://chdk.setepontos.com/index.php?topic=10579.msg104390#msg104390
Ported :   A1200    SD940   G10    Powershot N    G16

*

Online reyalp

  • ******
  • 12145
Re: 1.3 development planning thread
« Reply #17 on: 24 / August / 2013, 15:49:01 »
« Last Edit: 24 / August / 2013, 15:58:48 by reyalp »
Don't forget what the H stands for.


*

Online reyalp

  • ******
  • 12145
Re: 1.3 development planning thread
« Reply #18 on: 25 / August / 2013, 18:27:31 »
Some misc bugs
* interrupting lua script with shutter has issues, sometimes causes a lua assert (ignored by default in our implementation), stuff with a yield can't be used in restore
* can't generate a long press of the alt button to canon firmware: http://chdk.setepontos.com/index.php?topic=10580.msg104442#msg104442
Don't forget what the H stands for.

*

Online reyalp

  • ******
  • 12145
Re: 1.3 development planning thread
« Reply #19 on: 14 / June / 2014, 22:44:57 »
Bump.

I think it's about time to start thinking about a 1.3 release. The current trunk seems pretty stable, and there are some major improvements. waterwingz MF improvements and the FsIo crash fix both come to mind.

If there are outstanding problems or uncompleted features in 1.3 that should be finished before release, please collect them them here.

Some items on my list:
* Resolve as many of the outstanding issues with focus override (cases where it crashes or stops working)
* Make sure the no-script SD overrides (menu override, bracketing, MF shortcuts) behave somewhat sanely, or at least no worse than 1.2
* integrate srsa's console hook work http://chdk.setepontos.com/index.php?topic=11029.0
* implement the metering stuff needed to use shoot hooks (http://chdk.setepontos.com/index.php?topic=11081.0) to replicate lapsers continuous timelapse stuff
Don't forget what the H stands for.

 

Related Topics