zwierzak Posted September 26, 2011 Posted September 26, 2011 (edited) Hello, I would like to ask you for help once more I would like to write a function, that can recieve n-parameters. Here is an example: Func test(1[,...n]) ;... EndFunc Here, the function requires at least 1 argument. Later on, inside the function it will be determined, whether the function needs 1,2 or 3 arguments. For example, when i call test(1) the function in fact will require 3 more arguments, so it should look like that: test(1,10,15,5). To be precise, when I for example put 2 as a first argument - the function will need 5 more arguments, so the call process should look like: test(2,10,15,5,6,20). I hope that you've managed to understand what is my desire Here is an example from help(DllCall function) DllCall ( "dll", "return type", "function" [, type1, param1 [, type n, param n]] ) Edited September 26, 2011 by zwierzak
Mat Posted September 26, 2011 Posted September 26, 2011 The only way to ensure the number of arguments has a ridiculously big limit is to pass an array. I won't say unlimited though AutoIt Project Listing
water Posted September 26, 2011 Posted September 26, 2011 As the number of parameters to the function is variable you can only define 1 parameter as obligatory the rest has to be optional. Your script has to decide how many parameters are needed and then has to check if the user has passed all neccessary parameters. Func Test($Obligatory_Parameter, $Optional_Parameter1 = "", $Optional_Parameter2 = "" ....) ; Your code EndFunc My UDFs and Tutorials: Spoiler UDFs: Active Directory (NEW 2024-07-28 - Version 1.6.3.0) - Download - General Help & Support - Example Scripts - Wiki ExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example Scripts OutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - Wiki OutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - Download Outlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - Wiki PowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - Wiki Task Scheduler (2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki Standard UDFs: Excel - Example Scripts - Wiki Word - Wiki Tutorials: ADO - Wiki WebDriver - Wiki
zwierzak Posted September 26, 2011 Author Posted September 26, 2011 (edited) You mean that it is better to make it this way? Func Test($Obligatory_Parameter, $Array_Parameters) ;... Endfunc I wonder if you could give me a working example? Edited September 26, 2011 by zwierzak
Mat Posted September 26, 2011 Posted September 26, 2011 #include <Array.au3> Local $args[3] = [10, 15, 5] Test(1, $args) Local $args2[5] = [10, 15, 5, 6, 20] Test(2, $args2) Func Test($Obligatory_Parameter, $Array_Parameters) MsgBox(0, 'Test: ' & $Obligatory_Parameter, _ArrayToString($Array_Parameters, ',')) EndFunc In reality you'd cheat and use: #include <Array.au3> Test(2, StringSplit('10,15,5,6,20', ',', 2)) Func Test($Obligatory_Parameter, $Array_Parameters) MsgBox(0, 'Test: ' & $Obligatory_Parameter, _ArrayToString($Array_Parameters, ',')) EndFunc That should work in theory, though I haven't tested it. AutoIt Project Listing
zwierzak Posted September 26, 2011 Author Posted September 26, 2011 (edited) Isn't there any other way to make this function look normal? I mean that I am writing an UDF and i wouldn't like the users to type something like this:Test(2, StringSplit('10,15,5,6,20', ',', 2)) when calling a function. I would like it to look like Test(2,10,15,5,6,20). Is there any way to place this StringSplit part inside the function? The developers of au3 did manage to place this part inside the function when I look at dllcall Edited September 26, 2011 by zwierzak
AdmiralAlkex Posted September 26, 2011 Posted September 26, 2011 Look at water said above and look at @NumParams in the helpfile .Some of my scripts: ShiftER, Codec-Control, Resolution switcher for HTC ShiftSome of my UDFs: SDL UDF, SetDefaultDllDirectories, Converting GDI+ Bitmap/Image to SDL Surface
BrewManNH Posted September 27, 2011 Posted September 27, 2011 You'd be better off using an array to send to the function, that way the array can be of any size, which can change every time you call the function. If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag GudeHow to ask questions the smart way! I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from. Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays. - ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script. - Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label. - _FileGetProperty - Retrieve the properties of a file - SciTE Toolbar - A toolbar demo for use with the SciTE editor - GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI. - Latin Square password generator
Spiff59 Posted September 27, 2011 Posted September 27, 2011 The variation of the same thing that best "looks normal" might be just wrapping the parms in quotes: #include <Array.au3> Test(1, "10, 15, 5, 6, 20") Func Test($Obligatory_Parameter, $Array_Parameters) $parms = StringSplit($Array_Parameters, ",") _ArrayDisplay($parms) EndFunc
Mat Posted September 27, 2011 Posted September 27, 2011 Be very careful with spaces. Could give parameters a rather different meaning. AutoIt Project Listing
zwierzak Posted September 27, 2011 Author Posted September 27, 2011 Ok, thank you very much guys. You've helped me a lot! The topic can be closed now
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now