Author Topic: changelog of trunk including comments / devtalk  (Read 17190 times)

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #15 on: 10 / November / 2008, 11:41:05 »
Changeset 555 - chdk - Trac
+ add os.listdir to lua oslib, updated llibtst.lua
  syntax t=os.listdir("name",[showall])
  returns array of filenames, or nil, strerror, errno
  showall is a placeholder for a boolean value. If it is true, t includes ".", ".." and deleted entries
  NOTE except for the root directory, names ending in / will not work
« Last Edit: 11 / November / 2008, 08:58:32 by reyalp »
Don't forget what the H stands for.

Offline fudgey

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 1690
  • a570is
Re: changelog of trunk including comments / devtalk
« Reply #16 on: 10 / November / 2008, 23:52:45 »
  if showall is true, t includes ".", ".." and deleted entries

Nice!

Do you think this could lead way to in-camera undelete?

Offline PhyrePhoX

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 2254
  • make RAW not WAR
    • PhyreWorX
Re: changelog of trunk including comments / devtalk
« Reply #17 on: 19 / November / 2008, 05:40:55 »
added plasmaHHs patch that pimps the edge overlay feature in a major way

Quote
tadaa! major pimping of an already cool feature!
you can now SAVE and LOAD edge overlays! this was written by PlasmaHH (shy guy, only in irc :D)
Yes, you read it right:
- save an edge overlay: create an overlay (enable overlay and press half-press) -> go to overlay menu and press save
- load an overlay (go to menu and choose an *.edg file)
- create overlays from jpgs in playmode! (only works on cameras that have a "hardware" switch of play/recmode for now, because on for example s3is halfpressing the shutter activates rec mode!
- free memory by using the item in the edge menu (also you should disable edge-overlay)
changes / enhancements to the mod by me:
- together with the edge overlay the zoom setting is saved, so when you load the file after one year it zooms to the position your camera had when you shot it!
- added the option so that an edge overlay is "locked", meaning the edgeoverlay you loaded or just created is not overwritten in the osd at half-press (this checkbox is overwritten on each camera startup... no big deal, but i dont like it like that right now)
This is a really great feature (for example for LONG-TERM TIMELAPSES, or stop-motion movies, or vertigo-effect, or stereography... the list is endless :D)

* restructured the root menu (put imo the most often used items to the top, moved edge overlay from OSD menu to the root menu, moved remote params menu to the misc menu)

because of this new feature and all the new cams i upped the version to 0.8.0 already...
P.S: had to rewrite some of PlasmaHHs stuff (e.g. write -> fwrite), i hope i did everything correctly (it's working flawlessly on s3is and a620)


two bugs i noticed:
when saving overlays when you havent saved an image before, the overlays all have the wrong time & date (no big deal) - does this also happen on dryos cameras?
one issue i couldnt fix so far: when you load an edge overlay and also set the zoom - the camera doesnt notice that you set the zoom. so when you zoom from position 0 to position max, camera thinks that you still are at 0 - so you can not press the zoom OUT button - if you have to first press zoom in to be able to zoom out again (by zooming in i mean zoom to the max, by zooming out i mean zoom to 0). this also happens when you use zoom in script by the way.
now i dont know if this camera related or chdk code related. we could overcome this, if in set_zoom we actually press one of the zoom buttons, so camera "resets" it's internal "zoomsensor".

edit: got a report from hacki that on his dryos sx100 this feature isnt working at all, he can neither save edgeoverlays (they arent created in the filesystem) nor load them (he still had one from my previous test builds with write instead of fwrite). hm, so what does that mean? need more testers. dryos preferred.
edit2: after some research we have found out that it DOES work in dryos. however, the routine that "calculates" the filename for the *.edg file reports back wrong numbers, which causes the effect that all edgs in dryos are saved as edge_0001.edg, instead of increasing.
making the filename smaller to for example edg0001.edg doesnt fix this. i suspect the problem being in /trunk/core/edgeoverlay.c - chdk - Trac in the function get_edge_file_num , something dryos specific.
« Last Edit: 19 / November / 2008, 07:24:32 by PhyrePhoX »

Offline PhyrePhoX

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 2254
  • make RAW not WAR
    • PhyreWorX
Re: changelog of trunk including comments / devtalk
« Reply #18 on: 26 / November / 2008, 04:04:39 »
saving of edge overlays still is buggy in dryos - only saves edge_0001.edg all the time. length of the filename isnt the issue here (we tested with shorter names), so the error is in the get_edge_file_num somewhere, specific to dryos.

about #592

Quote
+ added define CAM_BRACKETING for cameras that have bracketing in original firmware (g7,g9,s2is,s3is,s5is - need propcase for the dryos ones!) for gui.c

still need these damn bracketing propcase on the dryos cameras, so please, someone with a g9 or a s5is find these out for me.


about #593

Quote
added a feature that allows using cfgs from a different camera by resetting "critical" settings on startup of the platform id doesnt match (more settings? less settings? need input)


well, as it turns out, switch cfgs between different camera models wasnt so dangerous as i thought, for example the alt_button setting already is reset on cameras that dont support it. i added a few settings that should be resetted when you switch camera model, nothing big though. maybe that function will be important in later releases.



Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #19 on: 30 / November / 2008, 12:02:25 »
#606
+ Lua string lib. This should behave exactly as documented in the lua manual.

This adds about 5kb to total CHDK size. It may be worth making the pattern matching functions compile time optional, as they account for the vast majority of this and are probably not needed by many scripts. Formatting could be optional too.

* Updated get_buildinfo to return two additional fields:
os: string, either "dryos" or "vxworks"
platformid: number

llibtst.lua is updated to test string lib, and no longer reports a listdir failure under dryos.

Also removed some redundant entries from sig_ref_vxworks_2.txt
Don't forget what the H stands for.

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #20 on: 30 / November / 2008, 15:42:31 »
#607
+ add lua functions for flash parameters (onboard flash memory, not light)
  num=get_flash_params_count() -- num is the number of parameters
  str,num=get_parameter_data(id) -- str is the parameter value as a lua string,
    which may contain embedded NULLs or other non-printable characters. If the size of the flash parameter is 4 bytes or less, a second value is returned, containing the parameter value as a number if the parameter id is invalid, or the parameter size is 0, then nil is returned.
  scripts/examples/paramdmp.lua contains an example
* added CAMERA_HAS_JOGDAIL for g7/g9/sx100is, and used it instead of checking individual camera defines

This will let you directly access the exposure counter, for example. However, parameter IDs are camera specific. Setting parameter values is not supported yet.
Don't forget what the H stands for.

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #21 on: 01 / December / 2008, 05:48:37 »
#608 fix isxdigit for dryos, should fix test failure for string lib
Don't forget what the H stands for.

Offline fe50

  • Guru Member
  • ******
  • Posts: 2608
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: changelog of trunk including comments / devtalk
« Reply #22 on: 01 / December / 2008, 06:21:57 »
#608 fix isxdigit for dryos, should fix test failure for string lib
Yes (on SD870 1.00C).

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #23 on: 14 / December / 2008, 06:54:12 »
#634
+ allow user to override location of PRIMARY.BIN files. Set PRIMARY_ROOT to a tree that mirrors what is under platform, either on the make command line or in buildconf.inc

This lets you keep all your primaries and IDA files in one place, saves disk space if you have multiple working copies, and lets you delete working copies without losing all your bins. You can also easily build a tree with or without generating stubs_entry.s

* use automatic MEMISOSIZE on some new ports that didn't have it: g9, sd30, sd300/100j
* clean up old commented MEMISOSIZE stuff

Don't forget what the H stands for.

CHDK Forum

Re: changelog of trunk including comments / devtalk
« Reply #23 on: 14 / December / 2008, 06:54:12 »

Offline fe50

  • Guru Member
  • ******
  • Posts: 2608
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: changelog of trunk including comments / devtalk
« Reply #24 on: 14 / December / 2008, 16:30:53 »
#634
+ allow user to override location of PRIMARY.BIN files. Set PRIMARY_ROOT to a tree that mirrors what is under platform, either on the make command line or in buildconf.inc

This lets you keep all your primaries and IDA files in one place, saves disk space if you have multiple working copies, and lets you delete working copies without losing all your bins. You can also easily build a tree with or without generating stubs_entry.s

GREAT !!
...reyalP - can you read my minds ?

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #25 on: 28 / December / 2008, 14:48:59 »
I've added the ability to build CHDKs version of lua for the host platform (windows, linux, ... mac is not tested!). In tools/hostlua do make all

The resulting lua executable will behave more closely to lua on CHDK than a generic implementation (the os lib modifications are available, numbers are ints, etc). This is the first step in a larger project of making an  environment to develop/test/debug lua scripts on the PC. This is inspired by fbonomi's dummy.lua, but will hopefully be more flexible and closer to how things are on the camera.

You should also be able to pre-compile lua files (but not the main file, because it still has to have the @ params.)

With lua available as standard on the host, we could also use it in the tools or build process.
Don't forget what the H stands for.

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #26 on: 29 / December / 2008, 08:43:11 »
#655 always turns symbols back on when the camera restarts :(
Don't forget what the H stands for.

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #27 on: 29 / December / 2008, 12:44:08 »
#656 boot logo is now stored in CHDK/DATA/logo.dat
This saves a couple K of memory.
If file is missing, splash screen is shown without chdk logo.
You can make custom logos if you figure out the format.

OPT_BOOTLOGO compile time option is removed, because it would only save a few hundred bytes. If someone wants to bring it back, I'd suggest making it affect the whole bootsplash, not just the logo part. This might save as much as 600 bytes ;)

As before, you can turn off the splash (including logo) in the misc options.
Don't forget what the H stands for.

Offline hiker_jon

  • Full Member
  • ***
  • Posts: 213
Re: changelog of trunk including comments / devtalk
« Reply #28 on: 18 / January / 2009, 09:40:58 »
Hi,
I haven't compiled a new build in a while.  Just got 679.  I'm wondering what is the two digit number that appears in the upper right when I half-press the shutter in play mode.  Somebody's debug message? or some new thing that I don't know about.

Thanks for any info,
Jon

Offline reyalp

  • Guru Member
  • ******
  • Posts: 4490
Re: changelog of trunk including comments / devtalk
« Reply #29 on: 18 / January / 2009, 09:55:12 »
Hi,
I haven't compiled a new build in a while.  Just got 679.  I'm wondering what is the two digit number that appears in the upper right when I half-press the shutter in play mode.  Somebody's debug message? or some new thing that I don't know about.

Thanks for any info,
Jon
Sounds like (part of ?) some OSD element is showing, maybe due to changed defaults or other display related changes. If you open up the OSD editor, you may be able to see whats in that position.

Doesn't happen on my cam.
Don't forget what the H stands for.

 


SimplePortal 2.3.3 © 2008-2010, SimplePortal