yet another personal build (archive) - CHDK Releases - CHDK Forum

yet another personal build (archive)

  • 117 Replies
  • 40934 Views
yet another personal build (archive)
« on: 02 / March / 2008, 16:19:01 »
Advertisements
edit by phyrephox:

this is the archive about jucifers personal build. it is now outdated and replaced by the new chdk. here: CHDK build
« Last Edit: 12 / June / 2008, 16:14:25 by PhyrePhoX »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

yet another personal build (archive)
« Reply #1 on: 02 / March / 2008, 18:05:43 »
Deleted
« Last Edit: 22 / April / 2008, 13:23:32 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline rchoi999

  • *
  • 17
  • A650is
yet another personal build (archive)
« Reply #2 on: 02 / March / 2008, 23:12:31 »
Sorry, just try your experimental build on my A650 1.00D but it just don't startup at all.

*

Offline msl

  • *****
  • 1269
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
yet another personal build (archive)
« Reply #3 on: 03 / March / 2008, 05:57:44 »
A460 test:

All new features are working.  :)

Nice additions  :)
CHDK-DE:  CHDK-DE links


*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
yet another personal build (archive)
« Reply #4 on: 03 / March / 2008, 07:09:19 »
kinda nice, but ... why 4x? Wouldn't a value of 5 or 10 be nicer?

Dunno, did it from a personal need. :] (= for changing the Tv override -setting faster)
How about something like this:
when shoot_half is pressed,
  - enum values would be changed by 4
  - numeric values by 5 (10?)
Also, numeric values would be changed
  - by 10 (100?), when zoom_in is pressed
  - by 100 (1000?), when zoom_out is pressed.
Is de-/incrementing values by 1000 really needed?

I think for menu navigation 4 is a good value.
Would zoom_in/out be a better modifier key?
Or even using zoom_in for 4 down, zoom_out for 4 up?

Also using func/set as +1 variable change is unnecessary IMO. How about using it as variable-reset?

I might make a test build for these next week, if no one else makes it before me. ;)


Sorry, just try your experimental build on my A650 1.00D but it just don't startup at all.

Have no idea why... :/ Does the newest trunk work unmodified?

*

Offline msl

  • *****
  • 1269
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
yet another personal build (archive)
« Reply #5 on: 03 / March / 2008, 07:28:12 »
Quote
Would zoom_in/out be a better modifier key?

This is not so good because not all cams have this keys!
CHDK-DE:  CHDK-DE links

yet another personal build (archive)
« Reply #6 on: 03 / March / 2008, 07:58:53 »
Deleted
« Last Edit: 22 / April / 2008, 13:23:53 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
yet another personal build (archive)
« Reply #7 on: 03 / March / 2008, 10:20:32 »
Hmm, perhaps then 3 would be a good number for enum-type variable ..thingies. Really didn't think about it very much when altering the code...

4 for navigating menus up/down.
For menu navigation should all three keys modify up/down? By same or different amount?

As for numeric values,
shoot_half for 10x,
zoom_in for 100x,
zoom_out for 1000x,

OR

zoom_in for 10x,
zoom_out for 100x,
shoot_half for 1000x?
Would latter be better, if shoot_half is "harder" to use?

Of course, in the end, all keys could be user-definable.

I guess file browser shoot_half(/zoom)-modifying up/down has to be done separately (doesn't work on my cam with this build).

A simple text editor would be nice. Unfortunately I don't have the skills to realize it. Yet. :]


A650 and A720 were fixed in trunk 314. Don't have the tools to recompile right now. If you don't have the time to wait, patch & compile yourself. It isn't that hard. :] Perhaps I'll make a new test build in a couple of days.
Which keys would be good for use as modifiers on cameras that don't have the zoom rocker(=A460?)?

(On a side note (to self), "can't" use zoom_in/out to directly jump up/down.)
« Last Edit: 03 / March / 2008, 10:33:41 by Jucifer »


yet another personal build (archive)
« Reply #8 on: 03 / March / 2008, 11:51:07 »
Deleted
« Last Edit: 22 / April / 2008, 13:24:12 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
yet another personal build (archive)
« Reply #9 on: 03 / March / 2008, 13:39:19 »
IMO the current method for 10s and so on would be much more useful, if the digit being de-/incremented was hilighted somehow. (edit: hm, it already is (was ;))
I think the 1 to 1000-skipping is mainly an S-series problem... Maybe a simple check (With shooting_get_tick_count? Was there even such a function?) could be added to prevent that.
Anyway, off to wait some more to get the stuff needed for the development environment... :]
« Last Edit: 04 / March / 2008, 10:08:15 by Jucifer »

 

Related Topics