Author Topic: the collaborative CHDK build  (Read 79114 times)

Offline fudgey

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 1690
  • a570is
Re: the collaborative CHDK build
« Reply #135 on: 21 / August / 2008, 12:35:30 »
Hmm judging from the forum download counts and the actual behavior+reports here (I can't compare the patches and assembla history atm.) juciphox 486 adds the "wrong" patch that indeed causes several inconvenient things, see http://chdk.setepontos.com/index.php/topic,1849.msg17482.html#msg17482.

I believe I'm using http://chdk.setepontos.com/index.php/topic,1849.msg17451.html#msg17451 <-- this one in my patched trunk build, with the blink mode change in that thread.

Offline dzsemx

  • Sr. Member
  • ****
  • Posts: 299
  • [A650][A630]
Re: the collaborative CHDK build
« Reply #136 on: 21 / August / 2008, 12:53:28 »
:) wrong patch... great...
but right now only a few people is reporting bugs.. that's sad :(
btw... i need some programming exercises :D i going to forget programming :P
so i added an all mini histogram mode in my personal build:) and fixed that zebra + transparent osd problem, but probably still there are some bugs
« Last Edit: 21 / August / 2008, 14:37:28 by dzsemx »

Offline Hacki

  • Sr. Member
  • ****
  • Posts: 352
  • SX100
Re: the collaborative CHDK build
« Reply #137 on: 21 / August / 2008, 17:37:49 »
Quote
but right now only a few people is reporting bugs.. that's sad

Maybe because only a few people are experiencing bugs, or perceive something as bug?

On my camera everything OSD related works just fine.

The filebrowser font hast hat black outline, but actually i like it. I was the one picking out that patch from the thread, but i honestly didnt read the thread very carefully - i just picked the latest patch. And after some tinkering around, it worked with my cam.

Offline bperrybap

  • Rookie
  • *
  • Posts: 9
Re: the collaborative CHDK build
« Reply #138 on: 21 / August / 2008, 23:10:08 »
Quote
but right now only a few people is reporting bugs.. that's sad

Maybe because only a few people are experiencing bugs, or perceive something as bug?

On my camera everything OSD related works just fine.

The filebrowser font hast hat black outline, but actually i like it. I was the one picking out that patch from the thread, but i honestly didnt read the thread very carefully - i just picked the latest patch. And after some tinkering around, it worked with my cam.

Really?
Have you set your OSD background to "transparent", color = 0x0 and turned on the clock with seconds
or set the battery to report voltage?
Is the int_incr multiplier value stuff working for you?

The problem I see is that when OSD characters are drawn, when the background is transparent, it leaves whatever was there
previously. This means that the prior character is not erased but overwritten.
After a few updates, the character will no longer be readable.

In my opinion, while it does look "nice", "cool", or "better",  to have the transparent background
that allows OSD text to be closer to other camera text/icons, the current character draw code doesn't work well enough use.

I think that this could be made to work, but I don't think it will be as simple as what the current code is doing.

Adding in the check for shutter half pressed isn't a solution. It merely disables the transparent background feature
for any OSD text written when the shutter
is not pressed so you lose the "better" looking visual that the transparent background code was trying to enable.
The half pressed shutter patch solution merely makes it "work" better, when the shutter is not pressed.
It makes it work like it used to work before this transparent background capability was added.
The problem shows up again as soon as you press and hold the shutter button half way down.
Often it may not be seen because there can be a lot of stuff going on on the screen and things are being overlapped or
the screen is being repainted in the case of zebra modes, but it is is still there.

Disable, zebra and enable the clock with seconds and you will see the seconds digits overwrite each other
when the shutter is half pressed.
Also, play with the int_incr stuff. (press the zoom lever to set the integer increment values up/down).
This code will not erase the old text so that you will only see the values increment.

Using a transparent OSD background did work prior to this update.
The transparent background would erase the other text/icons if it overlapped it but it didn't
have all the issues with creating unreadable characters and breaking the int_incr feature as well.

Again, I think that this capability is really cool and can be made to work for OSD text,
but I believe that to do it right will not be easy and requires a more general solution than
what was being done in the draw_char() function.


So my feeling is that since this new transparent feature doesn't really fully work,
lets pull it out until it can be made to work properly.



--- bill


Offline Hacki

  • Sr. Member
  • ****
  • Posts: 352
  • SX100
Re: the collaborative CHDK build
« Reply #139 on: 22 / August / 2008, 00:08:16 »
Quote
Really?

No.

Quote
Have you set your OSD background to "transparent", color = 0x0

No.

Quote
Is the int_incr multiplier value stuff working for you?

No. Seems like i didnt read carefully enough. My bad. sorry.

Quote
So my feeling is that since this new transparent feature doesn't really fully work,
lets pull it out until it can be made to work properly.

Well. I'd say keep it in & try to fix  it. Juciphox isnt called "experimental" just for fun.





Offline fudgey

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 1690
  • a570is
Re: the collaborative CHDK build
« Reply #140 on: 22 / August / 2008, 00:22:10 »
The transparent part of it really is quite terrible as it introduces a lot of weird behavior that would need fixing (few examples being the battery indicator, ugliness of file browser at least on cameras with cheap LCDs like my a570is, histogram being drawn quite randomly when both zebra and histogram are enabled and "draw over zebra: OSD" is selected).

I can't begin to tell how beautifully the zebra patch works without the transparency. :D

Offline dzsemx

  • Sr. Member
  • ****
  • Posts: 299
  • [A650][A630]
Re: the collaborative CHDK build
« Reply #141 on: 22 / August / 2008, 15:53:17 »
war  :haha
forum members - like us - are to report bugs, no? :D
to help developers to feel happy  :P

ejsp

  • Guest
Re: the collaborative CHDK build
« Reply #142 on: 23 / August / 2008, 05:08:41 »
On my a460 I could use L/R toggle instead of up/down(zoom in/out). with zoom and quality switch--they both change...

I'll write a patch for that as soon as I compile gcc-arm-elf etc. (4.1.2)
If I can find where it is...

Thanks for all the great work juciphox.
« Last Edit: 23 / August / 2008, 07:09:03 by ejsp »

Offline brainwash

  • Jr. Member
  • **
  • Posts: 95
  • Nikon D40x & A460
Re: the collaborative CHDK build
« Reply #143 on: 23 / August / 2008, 05:31:59 »
Quote
but right now only a few people is reporting bugs.. that's sad

Maybe because only a few people are experiencing bugs, or perceive something as bug?

On my camera everything OSD related works just fine.

The filebrowser font hast hat black outline, but actually i like it. I was the one picking out that patch from the thread, but i honestly didnt read the thread very carefully - i just picked the latest patch. And after some tinkering around, it worked with my cam.
I'm just so used with my job as a developer that I usually work around bugs without giving a second thought to them. I'm not that picky when it comes to experimental software if there's a workaround somewhere. I did notice some strange behavior but most of the errors are recoverable. Perhaps I should start submitting bug reports but that may look like quality has gone down - it hasn't.

CHDK Forum

Re: the collaborative CHDK build
« Reply #143 on: 23 / August / 2008, 05:31:59 »

ejsp

  • Guest
Re: the collaborative CHDK build
« Reply #144 on: 23 / August / 2008, 07:01:41 »
Not sure what the problem is (still on 4.1.2)
Did I miss something on the linux compile guide?

>> Entering to core
gui.c -> gui.o
In file included from gui.c:32:
curves.h:15: error: array type has incomplete element type
make[1]: *** [gui.o] Error 1
make: *** [all-recursive] Error 1

Offline julianocs

  • Newbie
  • *
  • Posts: 2
Re: the collaborative CHDK build
« Reply #145 on: 31 / August / 2008, 01:11:46 »

Offline PhyrePhoX

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #146 on: 31 / August / 2008, 14:14:53 »
funny this wasnt reported before. should be fixed now :) (wait about half an hour until the autobuild server updates)

Not sure what the problem is (still on 4.1.2)
Did I miss something on the linux compile guide?

>> Entering to core
gui.c -> gui.o
In file included from gui.c:32:
curves.h:15: error: array type has incomplete element type
make[1]: *** [gui.o] Error 1
make: *** [all-recursive] Error 1

hm, everything compiles fine in linux AND windows shell. or does allbest compile on your system?

Offline fudgey

  • Global Moderator
  • Guru Member
  • *****
  • Posts: 1690
  • a570is
Re: the collaborative CHDK build
« Reply #147 on: 31 / August / 2008, 14:40:38 »
Bug report:

Building with fw dump in place is broken for a720 because a720/sub/100c/stubs_entry.S has NHSTUBS for temperature and sound things that belong to stubs_entry_2.S.

Automatic signature search overwrites stubs_entry.S and makes those stubs go missing causing build to fail since the functions in question aren't even searched for by the signature finder.


Offline julianocs

  • Newbie
  • *
  • Posts: 2
Re: the collaborative CHDK build
« Reply #148 on: 31 / August / 2008, 14:49:08 »
Hi,

Build 494 is working fine now on my SX100IS 1.01b.
Thanks and congratulations for this great mod.

Juliano

ejsp

  • Guest
Re: the collaborative CHDK build
« Reply #149 on: 01 / September / 2008, 22:07:54 »
The trunk compiles fine (r495) and it works perfectly fine on my cam.
Juciphox-r495 still doesn't compile with the same error.

 


SimplePortal 2.3.3 © 2008-2010, SimplePortal