Quote from: msl on 11 / December / 2014, 17:45:27Great. The alternative script header is a very nice improvement. Strings instead of index values would be nice. Even better would be a variable as table (index + string). Is it also possible to define a range for the big numbers? Or is this too complicated?My test code:Code: [Select]--[[@title parameter test#test_number=250 "numbers" [-500 500]#test_long=1000000 "big numbers" long [0 5000000]#test_value_id=0 "value id" {val_1 val_2 val_3}#test_bool=1 "bool" bool]]print("number:", test_number)print("big number:", test_long)print("value id:", test_value_id)print("bool:", test_bool)mslThanks for testing.Having a range on the 'long' value is currently not available - this is mainly because of the 16bit limit on the min & max values for range. This limit is from the menu system - to save space the min & max are packed into a single int.This could be fixed by storing both as 32 bit values; but this will cost a chunk of memory (there are a lot of menu items).The table option is a good idea, now I just have to figure out how to implement it Phil.
Great. The alternative script header is a very nice improvement. Strings instead of index values would be nice. Even better would be a variable as table (index + string). Is it also possible to define a range for the big numbers? Or is this too complicated?My test code:Code: [Select]--[[@title parameter test#test_number=250 "numbers" [-500 500]#test_long=1000000 "big numbers" long [0 5000000]#test_value_id=0 "value id" {val_1 val_2 val_3}#test_bool=1 "bool" bool]]print("number:", test_number)print("big number:", test_long)print("value id:", test_value_id)print("bool:", test_bool)msl
--[[@title parameter test#test_number=250 "numbers" [-500 500]#test_long=1000000 "big numbers" long [0 5000000]#test_value_id=0 "value id" {val_1 val_2 val_3}#test_bool=1 "bool" bool]]print("number:", test_number)print("big number:", test_long)print("value id:", test_value_id)print("bool:", test_bool)
--[[#test_table=0 "table" {label1 label2 label3} table]]print("test:", test_table.value, test_table.label)
Thx.Works fine . Something different than I thought, but a very good solution.msl
--[[#test_table=0 "table" {label1 label2 label3} table]]print("test:", test_table.value, test_table[test_table.value]) -- prints selected value and labelprint(test_table[0]) -- prints 'label1'
Is this a better solution?
--[[@param a test@default a 0@values a string1 string2 string3]]test_table = {string1, string2, string3}print(test_table[a+1])
Quote from: philmoz on 19 / December / 2014, 15:36:48Is this a better solution?Yes, that was my first thought for a table solution. With the old variant (@values) you always have to create a table. Code: [Select]--[[@param a test@default a 0@values a string1 string2 string3]]test_table = {string1, string2, string3}print(test_table[a+1])With the new proposal is it much easier.msl
I've always thought that it would be nice if CHDK actually used the values in each camera's shooting.c file for aperature_size_table[ ] , shutter_speeds_table[ ], and iso_table[ ] for something more useful. One obvious thought would be to use the data there as the values available for custom Tv, Sv, and Av input fields in script parameters.In theory, these tables are tuned to the actual values each camera can use so that's even more powerful. (Ignoring the possibility that many of them might have been C&P'd from other cameras).
#name=1 "title" bool
I started writing up the new syntax for the wiki cross-reference page by looking at philmoz's patches. I think I have most of what it sorted out but :Code: [Select]#name=1 "title" boolkind of jumps out relative to the 0/1 vs false/true Lua discussion. I realize it's a limitation of the current get_default() code in gui_script.c and will be non-trivial to fix so I'm "just sayin'" at this point.
#name=true "title" bool
Do you mean you want to be able to use 'true' and 'false' as the initialiser value?
Quote from: philmoz on 21 / December / 2014, 13:47:01Do you mean you want to be able to use 'true' and 'false' as the initialiser value?Correct. Seems consistent with how a Lua script should work?
--[[@title lua lib test@param a skip io@default a 0@param b skip all os@default b 0@param c skip os time@default c 0@param d skip os time fmt@default d 0@param e skip os filesystem@default e 0@param f skip string@default f 0]]do_io=a==0do_os=b==0do_time=c==0do_fmtdump=d==0do_dir=e==0do_string=f==0
--[[@title lua lib test#do_io=true "test io"#do_os=true "test all os"#do_time=true "test os time"#do_fmtdump=true "test os time fmt"#do_dir=true "test os filesystem"#do_string=true "test string"]]
Started by waterwingz Feature Requests
Started by Yariv Script Writing
Started by TedHTL Script Writing
Started by pigeonhill General Discussion and Assistance
Started by reyalp Feature Requests
