Adding new cameras, applying patches into trunk (with source code prepared) - page 59 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 54 55 56 57 58 [59] 60 61 62 63 64 ... 168   Go Down

Adding new cameras, applying patches into trunk (with source code prepared)

  • 1672 Replies
  • 706963 Views
*

Offline jstanley0

  • **
  • 71
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #580 on: 05 / December / 2011, 07:56:58 »
Advertisements
Make the IXUS220 use the _PT_MoveOpticalZoomAt() path instead of _MoveZoomLensWithPoint(), since the latter does not notify the JPEG engine of the new focal length, causing incorrect lens distortion correction to be applied.

Example of the problem here.
Logged
*

Offline waterwingz

  • ******
  • 12134
    • Waterwingz
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #581 on: 05 / December / 2011, 22:16:41 »
Patch to allow icon visibility to track the DISP key in playback mode (CHDK already has this option in shooting mode).

Forum thread : http://chdk.setepontos.com/index.php?topic=7201
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline outslider

  • *****
  • 762
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #582 on: 06 / December / 2011, 18:38:45 »
@philmoz

I followed your suggestions, but I had to use almost only histogram-colors values, since they are defined for all cameras both in rec and play mode. Other colors as grey, yellow and others are not and might be confusing. So this is the best way I can implement this stuff. I hope that it doesn't add any mess to the CHDK and gives a few new possibilities. So - here's a zip with all these things.
Logged
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick
*

Offline tsvstar

  • ***
  • 231
Re: Adding new cameras, applying patches into trunk (with source code prepa
« Reply #583 on: 07 / December / 2011, 01:28:29 »
Quote from: philmoz on 06 / December / 2011, 14:23:32
Can you explain the steps to cause this in more detail please - I can't get the current editor or file selector to hangup in build 1457.

1. Set UserMenu=OnDire
2. Go to Alt mode
3. Run editor script and select file
4. Press ALT to go to None mode
5. Press ALT again. You go to User Menu but no one button works
« Last Edit: 07 / December / 2011, 04:28:25 by acseven »
Logged
*

Offline philmoz

  • *****
  • 3445
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepa
« Reply #584 on: 07 / December / 2011, 03:34:01 »
Quote from: tsvstar on 07 / December / 2011, 01:28:29
Quote from: philmoz on 06 / December / 2011, 14:23:32
Can you explain the steps to cause this in more detail please - I can't get the current editor or file selector to hangup in build 1457.

1. Set UserMenu=OnDire
2. Go to Alt mode
3. Run editor script and select file
4. Press ALT to go to None mode
5. Press ALT again. You go to User Menu but no one button works

Thanks for that - looks like it affects any script, not just the editor.
I've made a change in changeset 1459 that stops the user menu from being opened if a script was running.

Phil.
« Last Edit: 07 / December / 2011, 04:28:23 by acseven »
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline tsvstar

  • ***
  • 231
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #585 on: 09 / December / 2011, 08:46:34 »
In attachment fix for get_config_value()/set_config_value() for LUA.
It incorrectly works with fields different from simple int/color: OSD_pos, int array, strings.

Reason: 1)using of wrong defines when process values; 2) plain CONF list.

Test script:
Code: [Select]
print_screen(2)
show_osd=get_config_value(1);
conf_batt_volts_max=get_config_value(8);
ubasic_vars_table=get_config_value(5);
histo_pos1,histo_pos2=get_config_value(21);
conf_reader_file=get_config_value(38);

print("show_osd="..show_osd);
print(";conf_batt_volts_max="..conf_batt_volts_max);
print(";histo="..histo_pos1..","..histo_pos2);
print("conf_reader_file="..conf_reader_file);
print("ubasic_v"..ubasic_vars_table[1]);
Logged
*

Offline philmoz

  • *****
  • 3445
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #586 on: 09 / December / 2011, 16:26:25 »
Quote from: tsvstar on 09 / December / 2011, 08:46:34
In attachment fix for get_config_value()/set_config_value() for LUA.
It incorrectly works with fields different from simple int/color: OSD_pos, int array, strings.

Reason: 1)using of wrong defines when process values; 2) plain CONF list.


Added in changeset 1462.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline waterwingz

  • ******
  • 12134
    • Waterwingz
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #587 on: 12 / December / 2011, 21:04:19 »
Patch to allow the CHDK OSD to track the state of the DISP key (so they are basically only visible when the Canon icons are also visible). 

This already works in shooting mode - this patch enables it in playback and review modes.  It is controlled from the OSD menu items "Hide In ?" and "Show OSD in Review Mode".  Requires an update to each cameras platform_camera.h file to identify the two param values that give the DISP key status in those modes.

Code: [Select]
#define PARAM_CAMERA_NAME     4   // parameter number for GetParameterData
#define PARAM_DISPLAY_MODE1  57  // param number for LCD display mode when camera in playback
#define PARAM_DISPLAY_MODE2  58  // param number for LCD display mode when camera in record view hold mode

Discussion here : http://chdk.setepontos.com/index.php?topic=7201

Reviewed with philmoz.

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline waterwingz

  • ******
  • 12134
    • Waterwingz
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #588 on: 13 / December / 2011, 00:10:57 »
Patch to move the scripts from the /CHDK/SCRIPTS/4Pack/lua & /CHDK/SCRIPTS/4Pack/uBasic directory to /CHDK/SCRIPTS.  This is suggested for two reasons.

1) DryOS R39 and later seem to have a path/file length limit of 32 characters so the current location causes every script but lua/hdr.lua to not load when selected.
2) The default /CHDK/SCRIPTS directory currently has no scripts in it (other than default.bas).  This change give new users some simple but useful scripts to try the first time they select the "Load Script from File ... " menu item.
« Last Edit: 13 / December / 2011, 00:13:23 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3445
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #589 on: 15 / December / 2011, 02:39:22 »
Quote from: waterwingz on 12 / December / 2011, 21:04:19
Patch to allow the CHDK OSD to track the state of the DISP key (so they are basically only visible when the Canon icons are also visible). 


Quote from: waterwingz on 13 / December / 2011, 00:10:57
Patch to move the scripts from the /CHDK/SCRIPTS/4Pack/lua & /CHDK/SCRIPTS/4Pack/uBasic directory to /CHDK/SCRIPTS.


Added in changesets 1484 & 1485.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
Pages: 1 ... 54 55 56 57 58 [59] 60 61 62 63 64 ... 168   Go Up
« previous next »
 

Related Topics