Returning value from a function

It isn't being unbound after the if. It's being unbound after the let - you should have put the retValue inside the let.

The general principle of many things in SKILL is that the return value is the last thing computed. So the return value of fileExists is the return value of the last statement in the function. If the retValue had been the last statement inside the let, the return value of the function would be the return value of the let; the return value of the let would have been the last value computed inside the let, i.e. retValue. retValue is no longer in scope if it's outside the let, which is why your code doesn't work.

So move the retValue one line up in the code and it will work.

Regards,

Andrew.

Thank you very much Andrew.

Regards,

José

Hi,

Regarding the script above, I have some more questions.

The script writes some configuration settings to a text file. When the script is launched for the first time it should check if "config.txt" exists on the script's directory, otherwise should create it.

I have tried using "./config.txt" but it doesn't work. Is there any reason for this ? Shouldn't this refer to the current directory where I am opening the script from ?

Regards,

José

Hi José,

When you open files without a directory component (so "config.txt") it will search for them using the SKILL path (getSkillPath()/setSkillPath()). If you give a directory (so "./config.txt") it will be relative to where you're running virtuoso. So it's the directory that getWorkingDir() returns.

That should work reliably. It's not necessarily the same place as the script is located.

Regards,

Andrew.

Hi Andrew,

But how can I force it to look in the script's directory ?

Thanks, José

If you have code in the file containing the script which runs as the file is loaded, you can use:

get_filename(piport)

to find the path name for the script. You could use this code below to get the full path for that resolving the SKILL path:

ABfindFileOnPath(get_filename(piport))

From that you could remove the trailing part of the filename to find the directory. For example:

pattern=pcreCompile("/[/]*$")
dirName=pcreReplace(pattern ABfindFileOnPath(get_filename(piport)) "" 1)

* ABfindFileOnPath.il

Author     A.D.Beckett
Group      Custom IC (UK), Cadence Design Systems Ltd.
Language   SKILL
Date       Mar 10, 2005 
Modified   
By         

SKILL Lint score: 100

***************************************************

SCCS Info: @(#) ABfindFileOnPath.il 03/11/05.11:37:35 1.2

*/

/******************************************************************
*                                                                 *
*                   ABfindFileOnPath(fileName)                    *
*                                                                 *
* Given a filename, return the full path to it. It uses the SKILL *
*    path if it is a file that doesn't begin with a number of     *
*    prefixes. If it is searched using the SKILL path, it will    *
*    return nil if the file can't be found - it doesn't bother    *
*      checking that for other cases (although it could...)       *
*                                                                 *
******************************************************************/

procedure(ABfindFileOnPath(fileName)
    let((foundPath)
        ;----------------------------------------------------------------
        ; Unless it begins with ./ ../ ~ or /, try to find the
        ; file along the SKILL path
        ;----------------------------------------------------------------
        unless(rexMatchp("^./" fileName) ||
            rexMatchp("^../" fileName) ||
            rexMatchp("^[/~]" fileName)
            foundPath=exists(path getSkillPath()
                isFile(strcat(path "/" fileName)))
            if(foundPath then
                fileName=strcat(car(foundPath) "/" fileName)
            else
                fileName=nil
            ) ; if
        ) ; unless
        ;----------------------------------------------------------------
        ; Simplify to give the full path name
        ;----------------------------------------------------------------
        when(fileName simplifyFilename(fileName))
    ) ; let
) ; procedure

Something like that.

Regards,

Andrew 

Hi Andrew,

Thanks for you answer.

I have some questions more:

1- I have defined buttons on a form with the option ?buttonLayout 'OKCancelDef. Until this point everything is ok, but I want that the OK button to verify all the fields before closing the form and continuing the program. In the same way I would like Cancel to actually cancel the script execution completely and probably execute some callback before exiting.

Cadence documentation only talks about user predefined buttons. So if it is not possible to attach callbacks to the existing buttons then I should do something like: 

?buttonLayout '('Empty (myOKbutton  myOKbuttonCB) ...)

is this correct ?

2 - When I press either OK or Cancel in a form, can I retrieve that information ?

I tried "retValue=createMyform()" expecting retValue to contain either "t" or "nil", but it doesn't work that way ....

3 - I guess this is in-line with 1 and 2.

I would like to insert my own help description when clicking the help button.

Best regards,

José

Hi José,

A simpler solution would be to specify the callback for the form as a list of two callbacks. Usually you specify a single string (say), but if you look in the documentation you can specify the OK and Cancel action by specifying a list. Then you can have different callbacks for OK/Apply and Cancel. This is definitely simpler than adding back custom buttons each with a callback.

For your second question, generally speaking you shouldn't expect the form to return something. It's better practice to use the form callback to do the next phase of your operations. Why is that? Well, if you have an Apply button on the form, the call to hiDisplayForm() won't return - it only returns when you hit OK or Cancel (unless you have set ?dontBlock t when creating the form, in which case it returns immediately). So it's considered bad form (excuse the pun) to rely on the return value from hiDisplayForm().

For your third question, you can customise the help behaviour. It's not that straightforward, but it is covered in the documentation...

Regards,

Andrew.