CHDK PTP interface - page 45 - General Discussion and Assistance - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 40 41 42 43 44 [45] 46 47 48 49 50 ... 125   Go Down

CHDK PTP interface

  • 1244 Replies
  • 519604 Views
*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: CHDK PTP interface
« Reply #440 on: 14 / March / 2011, 07:51:57 »
Advertisements
Quote from: msl on 14 / March / 2011, 06:19:42
We have currently enough other options to delete files with CHDK.

Hmm.. I certainly won't argue with you.  I can understand why you are so hesitant to put in a potentially destructive feature (delete files=destructive).  For me, the other methods aren't "easy" enough, and so I keep sticking this code in for myself.  It's not a problem though.

I also understand that the things I am working on are not really important to the rest of the world, but to me they are and so I keep doing them!  It is good to learn, and I'm enjoying playing with CHDK, Lua code, UBasic, and AutoIt. 

Last night I made an external help file for the gui, and I'm trying to pull together a good enough PTPCamGUI help file that explains how to use each feature.  I'm also trying to get the timelapse section to have start delays, etc.. more like the intervalometer scripts.  Why?  Because I don't have a job, and it keeps me busy!  ::)
Logged
Don't let the sands of time get in your lunch.
*

Offline rudi

  • ***
  • 129
  • A590IS_101B, SX260HS_100B
Re: CHDK PTP interface
« Reply #441 on: 15 / March / 2011, 11:54:06 »
Quote from: reyalp on 14 / March / 2011, 00:37:12
return strangeness:
Sorry reyalp, I have not enough time in this moment, so only a short comment.
I tested many options for two month ago (rev.1032 to 1033) to find the reason for return-fail. An easy way for gcc4 was to put $(OPT_OBJS) in core/Makefile to begin of line.

rudi
Logged
*

Offline reyalp

  • ******
  • 14113
Re: CHDK PTP interface
« Reply #442 on: 15 / March / 2011, 15:50:05 »
Quote from: rudi on 15 / March / 2011, 11:54:06
Sorry reyalp, I have not enough time in this moment, so only a short comment.
I tested many options for two month ago (rev.1032 to 1033) to find the reason for return-fail. An easy way for gcc4 was to put $(OPT_OBJS) in core/Makefile to begin of line.

rudi
Thanks, this is very a good clue. I also don't have much time during the week, but this gives me something work on.
Logged
Don't forget what the H stands for.
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK PTP interface
« Reply #443 on: 16 / March / 2011, 06:59:55 »
ptpCamGui (use with CHDK Shell or stand alone from here):

Quote from: achillies on 14 / March / 2011, 01:28:28
I changed some lines and now that doesn't happen.  And Again.. the stuff for deleting after download is in here too (because I use it all the time).  Based on build 82.

Because it generally is desired, I have added also the changes for deleting image files after download - thx achillies. I've  slightly adjusted the code for a better integration in the GUI. Settings will be saved in ini file.

Use this function at your own risk! Perhaps pictures can be lost.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: CHDK PTP interface
« Reply #444 on: 16 / March / 2011, 18:00:14 »
 8)  No, Thank you!  (All of you!)  In a previous post I mentioned other GUI things I was working on such as Timelapse start delay and an external help file. I have those things finished, but I don't really know how you like to see the changes (one change at a time, or all of the changes at once). 

If someone like me makes changes, how would you all prefer to see them?
Logged
Don't let the sands of time get in your lunch.
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK PTP interface
« Reply #445 on: 17 / March / 2011, 12:16:34 »
Quote from: achillies on 16 / March / 2011, 18:00:14
If someone like me makes changes, how would you all prefer to see them?
The best way would be to generate a patch/diff file. But this is not necessary. We can also compare the current version with other versions and merge, e.g. with KDiff3.

Post the changed Autoit file. We need only the ptpCamGui.au3 file. ptpCamGui_Obfuscated.au3 is generated automatically.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: CHDK PTP interface
« Reply #446 on: 18 / March / 2011, 01:33:25 »
Attached are the Timelapse/Delay Changes. I don't know if anyone will use the "days" delay for anything, but it might be useful. I only included the ptpcamgui.au3 file this time. I am trying to understand focus and DOF bracketing, and that is where I will go next.  I have also been trying to figure out how to get the zoom level (0-127) to accurately show my cameras zoom or equivalent (5.0-60mm or 28-336mm).  I really do need to get a job and leave you guys alone for a while! :D

I don't know how I lost so many lines, but this last simple change to ptpcamgui.au3 completes my Timedelay changes.
1089 - CHANGED GUICtrlSetData($LTLCurPic, "")
TO 1089 - GUICtrlSetData($PTLDTime, 0)
« Last Edit: 20 / March / 2011, 13:06:33 by achillies »
Logged
Don't let the sands of time get in your lunch.
*

Offline msl

  • *****
  • 1280
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK PTP interface
« Reply #447 on: 18 / March / 2011, 06:01:27 »
Quote from: achillies on 18 / March / 2011, 01:33:25
Attached are the Timelapse/Delay Changes.
Sorry, there are no changes for time lapse in the attached file. The changes relate to the already built-in delete function.

msl
Logged
CHDK-DE:  CHDK-DE links
*

Offline achillies

  • ***
  • 227
  • SX130IS
Re: CHDK PTP interface
« Reply #448 on: 18 / March / 2011, 08:21:48 »
@msl - It looks like it's all there to me!  I also attached the text file with differences this time.  I will try to learn how to generate a better diff file.

EDIT - It was "mostly" there.  I missed a variable or two related to switching languages, and I'm sure since many of you are german, you hit it right away.  It has been fixed, and reposted in the message above. I apologize for not testing more carefully.  Attached to this message is the obfuscated version.  

Also, when I try to use CHDK-DE builds (sx130is compiled) with PTPCamGUI I can not take pictures. it seems to go into  a loop with ">> luar get_mode() << false (Length: 5)" repeating.  When I use the international builds (eg. 1089 patched with quids sx130is patch) everything works fine.  What might be the cause?  The CHDK-DE build seems to work well with this camera if I don't try to use PTPCamGUI (fresh version.. none of my new changes).
« Last Edit: 19 / March / 2011, 17:42:15 by achillies »
Logged
Don't let the sands of time get in your lunch.
*

Offline reyalp

  • ******
  • 14113
Re: CHDK PTP interface
« Reply #449 on: 20 / March / 2011, 00:03:46 »
Quote from: reyalp on 15 / March / 2011, 15:50:05
Quote from: rudi on 15 / March / 2011, 11:54:06
Sorry reyalp, I have not enough time in this moment, so only a short comment.
I tested many options for two month ago (rev.1032 to 1033) to find the reason for return-fail. An easy way for gcc4 was to put $(OPT_OBJS) in core/Makefile to begin of line.

rudi
Thanks, this is very a good clue. I also don't have much time during the week, but this gives me something work on.
A little more on this: Just moving $(OPT_OBJS) to not be the last item is sufficient. Trying the order of things within $(OPT_OBJS) seems like the next step, to narrow it down to the smallest change.

I still don't see why this is happening. It seems too consistent to be just something like value of uninitialized memory being different.

gcc4 is more sensitive to link order than gcc3. It seems possible that the linker could be picking up a different function for something depending on order. My first guess was the ctype functions (isspace/iscntrl etc) seem like they might be related, based on the problem with numeric return and newline, but if this is the case I don't see where.

I thought the fact that iscntrl was always false might be related, but fixing that doesn't change anything. I'll fix that in the trunk anyway, since lua patterns use it.

Core makefile uses
 --start-group $^  $(LDLIBS) --end-group

I wasn't able to find good documentation for --start-group and --end-group, but it seem to force the linker to repeatedly scan all the libs to resolve cyclic dependencies. $(LDLIBS) is only -lgcc which doesn't seem like it should have anything relevant.

edit:
good
 ... script.o console.o
bad
 ... console.o script.o

edit:
this seems specific to the order of script.o and console.o, putting other .o files later doesn't seem to change whether it works or not.
« Last Edit: 20 / March / 2011, 01:04:58 by reyalp »
Logged
Don't forget what the H stands for.
Pages: 1 ... 40 41 42 43 44 [45] 46 47 48 49 50 ... 125   Go Up
« previous next »
 

Related Topics
SimplePortal 2.3.6 © 2008-2014, SimplePortal