Now THAT'S what I call enhancements!
New:
- width/height of spacebar now toggable (between about 7 ("canvas" is about 6 pixels, so the actual minimum information bar can be set to ONE pixel, almost too small) pixels and 17 pixels, check it out)
That's much better than a very thin spacebar. Now people can choose.
I don't get what you mean by "between about 7". I see your code and it looks like the user can select from 10 different widths. But I'll try it in my camera tonite.
- New Warning tresholds introduced, you can choose between treshold in MB and Percent.
Very handy when taking a lot of continuous shots, I loose notion of memory space. Now I have almost everything I need for that beach setup.
- New RAW Counter treshold, you can set it so that the RAW counter blinks when for example under 10. Previous setting was hardcoded to 1. Also changed: No "Warning" String anymore, just blinking between warning color and OSD color.
- Raw Counter now enabled by default
As I said, that is very helpful. Now the camera reminds you when have a few shots before memory is full. Like the Boy Scouts, you can now "be prepared" when you know a number of action shots is comming.
I agree with Barney on that "too many options in menu" problem. I even was thinking about having a "Simple menu" and an "Advanced menu". So you can go to advanced from time to time only. But now that is solved in a much better way with fingalo's reconfigurable highly-adaptive user-customizable menu.
- new get statements available in ubasic: get_disk_size & get_free_disk_space - returns values in KB. you can build scripts now which stop when specific disk limit exceeded, for example.Divide by 1024 to have an "easier" calculation. This is my first fiddling around with ubasic, please test thoroughly.
That is a good adition. You can add them to the Wiki too! These new statemens remaind me I should get more into scripts because in the end, must of the problems can/should be solved with a simple script instead of "modifying the trunk"
as always: ugly code, i am relying on your advisories, tips & tricks to clean my code.
Unfortunately, I'm not that kind of programmer that can "see" the code and find probable errors or unineficient implementations. But someone mentioned that CHDK code is not very well commented. According to whim's cross referencing files the Ratio/Comment code is 0.31. To start commenting more than 100,000 lines of code sounds crazy. What we can do now is to comment our own input.
oh and another small question to the people who code for chdk but dont have write access to official trunk: how do you handle your code at home? have a local svn, but its always such a pain in the A$$ to make a diff vs. official trunk and merge when there is a new revision... any hints?
I'll second that question. I tried to download the trunk with Eclipse but I couldn't, no reading permissions, that's odd. I've been reading the svn manual but I guess input from more experienced developers would be very useful. May be we should start a new thread with this question. The other one where everybody states their editing environment only asks for that, no details.
Keep it going PhyrePhox, these additions really enchance our photography.
Poll
Poll
