alternative ways to start a script

waterwingz

12140

Re: alternative ways to start a script

« Reply #10 on: 24 / November / 2013, 17:24:01 »

Advertisements

Quote from: reyalp on 24 / November / 2013, 17:21:10

* the script set_autostart functions include the new value in the range check.

Thanks - missed that one.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3450

Re: alternative ways to start a script

« Reply #11 on: 25 / November / 2013, 04:19:20 »

Quote from: reyalp on 24 / November / 2013, 17:21:10

Note, I'm not sure if/how this interacts with the touchscreen UI stuff?

Works ok on the IXUS310.

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)

waterwingz

12140

Re: alternative ways to start a script

« Reply #12 on: 31 / January / 2015, 11:31:48 »

I'm back with one of my few remaining "wish list" items for CHDK : the ability to load & execute a script directly from the User Menu.

Some time ago, I prototyped something to see how this would work and posted sample screen shots here :
User Menu Editor module.
The UI changes were not great but seemed usable so over the last couple of days I coded a patch to implement what I had posted way back there.

But then I realized there is a much simpler way to do this! When the User Menu is active, if you should be able to press "shoot full" (rather than press "Func/Set") on any script name, the script loads and runs (rather than just loads).

Pressing "shoot full" anywhere else in the menus is simply ignored (unlike the conflicting uses of "shoot half" fwiw ..)

I realize this is yet another "secret CHDK button". But once you know it's there it should be really easy to remember as it should be intuitive that pressing the shutter button starts a script!

Patch file for 1.4.0 attached.

user_menu_script_run_v5.patch (1.42 kB - downloaded 22 times.)

« Last Edit: 31 / January / 2015, 13:17:39 by waterwingz »

Logged

Ported : A1200 SD940 G10 Powershot N G16

waterwingz

12140

Re: alternative ways to start a script

« Reply #13 on: 01 / February / 2015, 11:56:45 »

Patch file for an updated version attached ( 1.4.0 ).

Currently, CHDK menus are closed when you select a new script via the User Menu. This was done to allow the user to "quickly" activate the selected script but can be annoying if you are in the middle of setting up your camera via the User Menu and want to make further changes.

So I updated the patch such that selecting a script in the User Menu with the Func/Set button brings up an acknowledge text box and then returns to the User Menu. And as before, if you select the script with a "full press" then the menus close and the script launches.

I like this arrangement even better.

user_menu_script_run_v6.patch (1.77 kB - downloaded 21 times.)

Logged

Ported : A1200 SD940 G10 Powershot N G16

srsa_4c

4451

Re: alternative ways to start a script

« Reply #14 on: 01 / February / 2015, 18:32:16 »

I can see v5 as useful, but I don't get the point in v6. Some users may want to adjust script parameters prior to starting it, v6 would essentially remove that possibility.

Logged

waterwingz

12140

Re: alternative ways to start a script

« Reply #15 on: 01 / February / 2015, 18:56:22 »

Quote from: srsa_4c on 01 / February / 2015, 18:32:16

I can see v5 as useful, but I don't get the point in v6. Some users may want to adjust script parameters prior to starting it, v6 would essentially remove that possibility.

Sorry - not sure I follow.

In v6, the action when you do a "full press" is the same as v5.

But in v6, when you select the current script with Func/Set, it leaves you in the CHDK menus, where you can quickly go to the scripting menu to change parameters if necessary. In v5 (and the current code) you are dumped into plain <ALT> mode, where you need to press the menu button to get back into the CHDK menus or press Func/Set to get the script menu.

Logged

Ported : A1200 SD940 G10 Powershot N G16

srsa_4c

4451

Re: alternative ways to start a script

« Reply #16 on: 01 / February / 2015, 19:07:42 »

Quote from: waterwingz on 01 / February / 2015, 18:56:22

But in v6, when you select the current script with Func/Set, it leaves you in the CHDK menus, where you can quickly go to the scripting menu to change parameters if necessary.

Are we talking about the same user menu?
With v6, if I press SET on a script entry of the user menu, I get a nice message box that shows the script's full file name. My other option is to start the script by pressing the shutter.

Logged

waterwingz

12140

Re: alternative ways to start a script

« Reply #17 on: 01 / February / 2015, 19:23:42 »

Quote from: srsa_4c on 01 / February / 2015, 19:07:42

Are we talking about the same user menu? With v6, if I press SET on a script entry of the user menu, I get a nice message box that shows the script's full file name. My other option is to start the script by pressing the shutter.

Thanks for trying the patch. I think that we are talking about the same thing - those are the two option I was hoping to offer.

I added that message box because without it, pressing Func/Set button would leave you in the User Menu with no indication that anything had happened (as you can't see the currently loaded script when CHDK's menus are active). I also reused existing strings .. maybe I should have added one that says "Script successfully loaded" in that message box ?

Logged

Ported : A1200 SD940 G10 Powershot N G16

srsa_4c

4451

Re: alternative ways to start a script

« Reply #18 on: 01 / February / 2015, 19:39:05 »

Quote from: waterwingz on 01 / February / 2015, 19:23:42

I added that message box because without it, pressing Func/Set button would leave you in the User Menu with no indication that anything had happened (as you can't see the currently loaded script when CHDK's menus are active). I also reused existing strings .. maybe I should have added one that says "Script successfully loaded" in that message box ?

So, SET now selects a new script. I still don't see how this should speed up anything.
I click SET -> get the message box -> need to click SET again -> I'm still in the user menu. I have to leave ALT mode, re-enter ALT mode and click SET again to reach the script menu.
With v5 and without the patch, I'm instantly in ALT mode when I click SET, and I just need to click SET once again to reach the scripting menu.
Am I missing something?

Logged

waterwingz

12140

Re: alternative ways to start a script

« Reply #19 on: 01 / February / 2015, 21:15:34 »

Quote from: srsa_4c on 01 / February / 2015, 19:39:05

Am I missing something?

UI changes are tough. Something that works for you might not work for me.

So do we agree that being able to run a script directly from the User Menu (via a full presss) is a good thing?

If so, that leaves selecting the current script via Func/Set

I get what you are saying - it's just that I seldom spend much time fiddling with the @parameter values as I tend to set the defaults in the script to what I use by editing the source. The whole CHDK saving of 10 parameter sets has never really worked stably for me. So staying in the User Menu makes sense to me.

But you have given me a new idea that might work for both of us. How about when you press Func/Set on a script in the User Menu, you get that script loaded and you get moved to the Script menu? Seems like that might be just about perfect?

Logged

Ported : A1200 SD940 G10 Powershot N G16