changelog of trunk including comments / devtalk

  • 275 Replies
  • 60831 Views
Re: changelog of trunk including comments / devtalk
« Reply #30 on: 18 / January / 2009, 04:06:18 »
Advertisements
Sounds like seconds to me.

*

Offline Hacki

  • ****
  • 353
  • SX100
Re: changelog of trunk including comments / devtalk
« Reply #31 on: 18 / January / 2009, 04:30:57 »
Sounds like seconds to me.

Indeed. OSD Parameters -> Clock -> @Shutter halfpress show [Dont / Full / Seconds]


*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: changelog of trunk including comments / devtalk
« Reply #32 on: 18 / January / 2009, 04:37:32 »
If the default setting is seconds, it's probably not a very good default... to me the seconds only display looks like something's broken.

*

Offline PhyrePhoX

  • *****
  • 2253
  • make RAW not WAR
    • PhyreWorX
Re: changelog of trunk including comments / devtalk
« Reply #33 on: 18 / January / 2009, 04:45:52 »
but the clock is shown @ default as well, so normally you should get the meaning (unless you disabled the clock of course).


*

Offline reyalp

  • ******
  • 10168
Re: changelog of trunk including comments / devtalk
« Reply #34 on: 18 / January / 2009, 07:31:56 »
#683
https://chdk.kernreaktor.org/mantis/view.php?id=147 allocate zebra memory only when needed, frees when zebra not displayed.
this disables zebra in when scripts are running, could be made an option if needed. (if it ever displayed in the first place ?)
Also some cosmetic formatting changes.

based on fudgeys patch http://chdk.setepontos.com/index.php/topic,2885.0.html

#684
Make motion detector memory dynamic. Allocated when a script first uses md_detect_motion, freed when the script ends. Saves about 20K when you aren't running an MD script.
Also made md debugging code compile time optional. OPT_MD_DEBUG, default disabled. Saves about 1k.
Don't forget what the H stands for.

Re: changelog of trunk including comments / devtalk
« Reply #35 on: 18 / January / 2009, 11:42:13 »
Thanks reyalp,
That's all I needed to do (look at the OSD layout editor).  I was confused by the clock seconds display on half press in play mode.  Didn't have this feature in the previous builds I tried.

Jon

*

Offline fe50

  • ******
  • 3045
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: changelog of trunk including comments / devtalk
« Reply #36 on: 18 / January / 2009, 11:59:40 »
Hehe - since this is the default setting (Clock on & seconds while half-press) i always disable this when i use a autobuild package, in my own builds i disable it in the sources, e.g. with CHDK-Shell's pref-edit function... ::)

*

Offline reyalp

  • ******
  • 10168
Re: changelog of trunk including comments / devtalk
« Reply #37 on: 18 / January / 2009, 18:41:06 »
#687
make shot_histogram memory dynamic. Allocated on shot_histo_enable(1), deallocated on disable or script end.

This saves about 2k when you aren't using a script with shot_histogram.

edit:
#688
use cached memory for dng bad pixel list. This should be slightly faster, but wasn't a big part of the DNG shooting process to start with.
« Last Edit: 18 / January / 2009, 21:22:28 by reyalp »
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 10168
Re: changelog of trunk including comments / devtalk
« Reply #38 on: 22 / January / 2009, 21:43:51 »
 The memory crusade continues
#690
* dynamically allocate memory for curves. Memory is allocated when when a curve option and valid file are selected, and freed when curves are disabled.
* fix +1/+2 option
* eliminate some copy/paste code.

This saves about 20kb in builds with curves enabled, bringing total CHDK size for a default build of my camera under 300k for the first time in a very long time. Even when curves are enabled, less than 1/2 the previous amount of memory is required. Note that switching through options in the curve menu can bet a bit sluggish, since it loads the file immediately.
Don't forget what the H stands for.

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Changeset #695
« Reply #39 on: 28 / January / 2009, 16:35:45 »
http://tools.assembla.com/chdk/changeset/695
I have two questions to developers:

1. Why not create ps.fir directly:
Code: [Select]
$(PAKWIF) $(topdir)bin/PS.FIR  $(topdir)/bin/main.bin  $(PLATFORMID) 0x01000101

2. Why in one /Makefile we can see expressions like
$(topdir)bin/ and  $(topdir)/bin/  , where topdir=./ ? Maybe .//bin is not too correct path (for some programs)?

 

Related Topics