the collaborative CHDK build

  • 249 Replies
  • 111435 Views
*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: the collaborative CHDK build
« Reply #20 on: 15 / July / 2008, 01:23:15 »
Advertisements
While I was fooling around with it, I had the chdk menu suddenly disappear while I was navigating it a couple times; when

That happens to me on all builds. Just navigate the menu more and it reappears. For instance turning the camera causes the orientation detector to redraw things that might cause this, or at least once did.

I enabled the edge mode (which is spifftacular) the text of the chdk menus started going nuts, turning into gibberish, and

This one I haven't tried.

finally, while this build is loaded I can't seem to use a USB cable to download pics at *all*.  The camera and the computer act like the USB cable's not there.

You need to disable everything related to USB remote for USB image download to work...it's not a bug, but there could be a clear indicator on LCD to remind about this. I think this build has stuff imported from SDM, which means it's a bit different from Allbest in this regard.

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #21 on: 15 / July / 2008, 06:53:49 »
Edge overlay is highly experimental, and probably doesn't work properly on every cam.

USB connection to computer should work, when both remotes (script & scriptless) are disabled.

Also it's always a good idea to reset config(/rename/delete chdk.cfg) when switching to a new build. (Sometimes also necessary when updating to a new version of a build.)


How about a USB power indicator? When either remote is enabled and USB power is detected, show "USB remote enabled" (and which one) on screen?

*

Offline eheil

  • *
  • 12
Re: the collaborative CHDK build
« Reply #22 on: 15 / July / 2008, 09:25:59 »
USB connection to computer should work, when both remotes (script & scriptless) are disabled.

Cool, exactly where in the menus can I make sure "both remotes are disabled"?  I've never used remotes for anything, so I'm pretty unfamiliar with that aspect of CHDK.

Quote
Also it's always a good idea to reset config(/rename/delete chdk.cfg) when switching to a new build. (Sometimes also necessary when updating to a new version of a build.)

No worries, I usually blow away everything on the card when I upgrade. :)


*

Offline eheil

  • *
  • 12
Re: the collaborative CHDK build
« Reply #23 on: 15 / July / 2008, 09:29:50 »
Aha!  Under "Scripting Parameters" -- USB remote was enabled by default, that's what was getting me.  All is good now.  Thank you very much!


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #24 on: 15 / July / 2008, 10:16:35 »


How about a USB power indicator? When either remote is enabled and USB power is detected, show "USB remote enabled" (and which one) on screen?

#27 ;)
id'd love that!

Quote
Also it's always a good idea to reset config(/rename/delete chdk.cfg) when switching to a new build. (Sometimes also necessary when updating to a new version of a build.)
hm, are you sure? i think deleting cfg only has to be done when for example you switch to SDM and back. switching from "official trunk" to juciphox and back should be safe.
« Last Edit: 15 / July / 2008, 10:18:35 by PhyrePhoX »

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #25 on: 15 / July / 2008, 11:06:45 »
Now that I look at conf.c... I think one should reset config when switching to juciphox branch... (I reused some old, unused config IDs. *yet again some evil laughter* Of course those can be moved to the end of the table...)
When new entries are added to trunk's ConfInfo conf_info[] and then added to juciphox with the same numbers (so that the IDs of the following entries have to be incremented), juciphox users have to reset config when updating.
If the new entries are appended to the table, trunk users switching to juciphox have to reset config. What they have to do now anyway. ;)
Bottom line:
appending new IDs = good.
modifying the existing IDs = less good.
Though I'm not completely certain. :]


edit: the remote issue... Should the same enum-type selector be in both menus containing the remote enable -selection? (off - script - no-script - both)
« Last Edit: 15 / July / 2008, 11:12:29 by Jucifer »

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #26 on: 15 / July / 2008, 11:41:39 »
hah yes, you are right. fully forgot that the IDs are changing. so yes, one *should* delete the cfg when switching releases ;)
appending new ids for the win.

remote issue: we can call the remote submenu off of the script menu, in there you can also set the script-usb params, imo. no?

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #27 on: 15 / July / 2008, 12:39:24 »
Moving script-remote to the remote menu and calling that menu from script menu would be fine by me.
Now, should the remote menu have two places it can be opened from (edit: actually three, as I have it also in the user menu)?
« Last Edit: 15 / July / 2008, 14:59:19 by Jucifer »


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #28 on: 15 / July / 2008, 13:54:43 »
well yes, if it is possible?

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #29 on: 15 / July / 2008, 14:58:06 »
Can't see why not. I'll try it some day soon, if I have the enthusiasm & it's not yet committed. ;)

 

Related Topics