the collaborative CHDK build - page 15 - CHDK Releases - CHDK Forum
« previous next »
Pages: 1 ... 10 11 12 13 14 [15] 16 17 18 19 20 ... 25   Go Down

the collaborative CHDK build

  • 249 Replies
  • 177300 Views
*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: the collaborative CHDK build
« Reply #140 on: 21 / August / 2008, 15:22:10 »
Advertisements
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
Logged
*

Offline dzsemx

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

ejsp

Re: the collaborative CHDK build
« Reply #142 on: 22 / August / 2008, 20: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: 22 / August / 2008, 22:09:03 by ejsp »
Logged
*

Offline brainwash

  • **
  • 95
  • Nikon D40x & A460
Re: the collaborative CHDK build
« Reply #143 on: 22 / August / 2008, 20:31:59 »
Quote from: Hacki on 21 / August / 2008, 08: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.
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.
Logged
*

ejsp

Re: the collaborative CHDK build
« Reply #144 on: 22 / August / 2008, 22: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
Logged
*

Offline julianocs

  • *
  • 2
Re: the collaborative CHDK build
« Reply #145 on: 30 / August / 2008, 16:11:46 »
Logged
*

Offline PhyrePhoX

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

Quote from: ejsp on 22 / August / 2008, 22: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

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

Offline fudgey

  • *****
  • 1705
  • a570is
Re: the collaborative CHDK build
« Reply #147 on: 31 / August / 2008, 05: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.

Logged
*

Offline julianocs

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

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

Juliano
Logged
*

ejsp

Re: the collaborative CHDK build
« Reply #149 on: 01 / September / 2008, 13: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.
Logged
Pages: 1 ... 10 11 12 13 14 [15] 16 17 18 19 20 ... 25   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal