the collaborative CHDK build

[PhyrePhoX]

0.3.0:

+ added taskviewer by reyalp task viewer (vxworks only)
+ added Fishpeppers Boot Logo from here: chdk bootup logo mod
+ raw subtract for filebrowser by reyalp - raw subtract
* makefile changes:

    added several docs in the /docs dir, these are "catted" together during compilation -> one big readme file's gonna be put into the zip. Also includes camera specific notes, if existing (placeholders for now) (thx for helping with this, Hacki).

* Ixus 860is / SD870 - fixed ubasic_set_led (diff provided by FE50)
* patched symboldmod and changed splashscreen a little (diff sent in by CHDKLover)
* added toggle in scripts menu: now the saving of script params can be turned on/off (default: off)

btw in your latest patch in platform.h you did the following, reyalp:

-#define MODE_SCREEN_MASK        0x0C00
-#define MODE_SCREEN_OPENED      0x0400
-#define MODE_SCREEN_ROTATED     0x0800

was there a specific reason for this? because without this, it doesnt compile for example for s3is.

other than that, thanks for your work!


btw the switch (save_params) was added because we were getting reports that it does not work all the time and in some occasions even fubars the config file.

[reyalp]

PhyrePhox, that's probably a merge error on my part, I did move them in some other code I was working on, but it shouldn't have been in any of the patches you used.

[bperrybap]

Not sure if this is proper location for this information/bug report, but there is an issue with deleting user menu items.
When the menu item is deleted, you get a funky symbol left over.
It will go away after a power cycle.
I don't have my build environment set up yet, to test/verify this but
I believe this is caused by the code at line 737 of file gui.c

static CMenuItem blank_menu_item = {'0',LANG_MENU_ITEM_BLANK, MENUITEM_PROC, (int*)blank_menu,0};

It appears to be setting the symbol code to '0' instead of 0x0.

So it looks like this line should be:

static CMenuItem blank_menu_item = {0,LANG_MENU_ITEM_BLANK, MENUITEM_PROC, (int*)blank_menu,0};


-------------------------
There is also no symbol being used for the "Main Menu" item in the User menu.
Which I believe is handled on line 586 of gui.c

 {0x0,LANG_MENU_MAIN_TITLE,      MENUITEM_PROC,  (int*)rinit},

So it looks like this line should be: (with symbol code 0x20)

 {0x20,LANG_MENU_MAIN_TITLE,      MENUITEM_PROC,  (int*)rinit},

(based on root/main menu static init on line 729)

static CMenu root_menu = {0x20,LANG_MENU_MAIN_TITLE, NULL, root_menu_items };



Neither of these appear to be camera model specific.

--- bill

[reyalp]

A couple of small things for lua.
- fix the silly warning about ipow
- allow the use of 0x... for numeric constants.

[whim]

@reyalp

excellent work, finally 0 error/warning compiles where possible !
Thanks !

wim

[edit]
@all with svn access

3 more cams can easily be made to have 0 errors/warnings: A540, A640 and SX100IS.
they just need extra spaces+tabs removal (SX100IS) or LF adding (A540, A640) to
remove  "warning:  no newline at end of file"

[reyalp]

per Phyrephox request: raw develop in popup menu

not heavily tested, and I haven't updated the lang stuff.

edit:
silly me, just re-use the existing string

[PhyrePhoX]

added it. thanks!

edit: oh, you changed it. well, next time was kinda in a hurry.

also i moved the bitrate/quality osd thingy to the remaining video osd thingy. code is ugly though, as i have fixed positions, it's working though well maybe one can think of another way.

also added sx100 _b_ version (including the adresses in stubs file).

[mad_a720]

Hi!

I tested the juciphox build with my A720 - it's great! But I wonder how I can create a "BADPIXELS" directory on my SD card (4 GB, FAT) to use the hotpix removal. Thanx to the plural there are now 9 chars instead of 8 and my cam seems to have problems to find this directory (listed as "BADPIX~1"). However, I didnt get it running .

mad.

[fudgey]

Problem with juciphox 488 script menu feature "change multiplier using zoom lever":

Multiplier display in top left corner of the LCD only updates when increasing the multiplier (1->10->100 etc). It never updates on display when decreasing, even though the actual effective multiplier does change properly. Has worked on all trunk build I've used.

[dzsemx]

i noticed too...
the problem is related somehow (blank+transparent characters) to draw_char function which has been altered due cropped mode zebra and does not output any tranparent pixels

Cropped zebra or zebra specific OSD

after adding this tiny patch, it works...

[fudgey]

the problem is related somehow (blank+transparent characters) to draw_char function which has been altered due cropped mode zebra and does not output any tranparent pixels

Btw Ljl's patch does not implement cropped zebra. It's active over the entire display.

[dzsemx]

it was added as cropped zebra:)
https://tools.assembla.com/chdk/changeset/486

[bperrybap]

Guys, I am seeing many OSD problems with the changeset/486 updates.

The outlined text and transparent box concept is interesting, but
to me, the current bugs are so visible that the changes should be backed out until it is further tested and corrections are made.

Currently, when any OSD text value gets updated/changed it does not erase the previous text.
It overlays it on top of the old text so it quickly becomes unreadable.

The <ALT> prompt at the bottom also sometimes does not go away when exiting ALT mode.
The battery values clobber each other.
The time values will clobber each other.

Yes the tiny patch that checks for KEY_SHOOT_HALF does help but then the problem just shifts to when the
the shutter button is half pressed.
(Set up your clock to display seconds, to see the problem when the shutter button is pressed).

And by inserting in the key pressed check, you defeat what I thought the purpose of the transparent code was
trying to do, so visually, you are right back where you were without this (but with character black outlining).

I'm not feeling the value of this new transparent capability given its issues.

It is possible to do the character outlining *without* the special transparent checks until that code is properly fixed.

To do that change the last line of the multi if/else inside the draw_char() function in gui_draw.c

Code: [Select]

From:
else if(inside_box && cl>>8!=COLOR_TRANSPARENT) draw_pixel(x+ii ,y+i, cl>>8);

To:
else  draw_pixel(x+ii ,y+i, cl>>8);
That way the OSD works just like it did before but you have character outlining.


--- bill

[dzsemx]

yeah it's really buggy
my patch too:(
but it looks so much better the osd wihout background, i requested once that outlined characters would be nice:)
btw, changing that way will cut off many times the last coloumn of outline from the characters

[dzsemx]

why does "opt:" "ccd:" "batt:" strings have a leading space???