Is there a ULP dirty flag?

 

Just as a final note, below is my modification to check to see if a file

is writeable:

 

    //

    // A separate instance of Eagle will be invoked from the command line

    // to produce gerber files.  As such, it does not have access to objects

    // in this process's memory space and can only read from the disk.

    //

    // Therefore, it is imperative to make sure this board is saved

    before allowing

    // this program to continue.

    //

    string file;

    if(argv[1] != "saved") {

         // Get the file name out of the board.

         board(B) {

             file = B.name;

         }

 

         // Is it writable?

         if (system("test -w " + file) == 0) {

             // If so, save it.

             exit("write;\nrun camprep saved;\n");

         } else {

             // If not, give the user a chance to change his mind.

             if (dlgMessageBox("!<b>" + file + "</b>"

                 + "<p>The board file is not writable."

                 + "<p>CAM files will be built from last saved version.",

                 "&Continue", "&Abort") != 0) {

                 exit(0);

             }

         }

    }

 

Thanks for your input.

 

     - Chuck

You could try this. - Run it from a board

It less graceful but it does the job.

You attempt to open your board file in 'append' mode and the OS protests

(Win in my case).

string MyFile;

if(board) board(B) {MyFile = B.name;

fileerror();

output(MyFile,"aF"){}

if (fileerror()){

     dlgMessageBox(";I tried to open the board file in append mode.\nI

assume the file is read only or locked\n\nThe ULP will exit");

   exit(1);

     }

else dlgMessageBox("Hooray!\nI can write to the file "); exit(0);     

}

Warren

On 03/14/2016 08:25 AM, Chuck Huber wrote:

On 03/12/2016 02:51 PM, warrenbrayshaw wrote:

On 12/03/2016 10:59 a.m., Chuck Huber wrote:

 

Is there a flag associated with either a schematic or a board that

would

indicate if changes have been made since the last save? Perhaps

something like:

 

    board(B) {

         if (B.isDirty) {

             ...

         }

    }

 

 

I didn't see anything in the ULP manual like this.

 

Thanks,

     - Chuck

 

Hi Chuck

 

No, the 'modified flag' is not made available via the ULP language.

If you don't want your ULP to run if changes have not been saved, you

will have to invert your thinking and have the ULP save first, every

time, and then re enter the ULP.

 

e.g.

run your ULP

 

if(argv(n) != obscureNumber) exit("write; run ULP obscureNumber;");

...the rest if your ULP

 

Good morning, Warren,

 

That's what I currently do.  Here's a bit more detail on what I'm

encountering.  Most of the time, a board file is not checked out of

the change management system (Perforce) and is thus not writable.  So

when the UPL tries to save, I get several pop-up dialog boxes

indicating this condition and offering to Save As...

 

I guess I could check the file mode on the file first, something like

(in bash parlance):

 

    && save the file

 

I don't see a ULP equivalent to lstat(2), so I guess this might be a

job for the system() function.

 

    if(argv(n) != obscureNumber && system("test -w myfile.brd") == 0) {

        exit("write; run ULP obscureNumber;");

    }

    ...the rest if your ULP

 

I use this in a context where additional instances of eagle are

invoked to generate gerber files.  Obviously these child instances are

not aware of changes that have been made to the board in the parent

that have not been saved.

 

Thanks,

    - Chuck

 

Warren,

Just as a final note, below is my modification to check to see if a file

is writeable:

    //

    // A separate instance of Eagle will be invoked from the command line

    // to produce gerber files.  As such, it does not have access to objects

    // in this process's memory space and can only read from the disk.

    //

    // Therefore, it is imperative to make sure this board is saved

    before allowing

    // this program to continue.

    //

    string file;

    if(argv[1] != "saved") {

        // Get the file name out of the board.

        board(B) {

            file = B.name;

        }

        // Is it writable?

        if (system("test -w " + file) == 0) {

            // If so, save it.

            exit("write;\nrun camprep saved;\n");

        } else {

            // If not, give the user a chance to change his mind.

            if (dlgMessageBox("!

" + file + "

The board file is not writable."
+ "

CAM files will be built from last saved version.",

                "&Continue", "&Abort") != 0) {

                exit(0);

            }

        }

    }

Thanks for your input.

    - Chuck

On 03/12/2016 02:51 PM, warrenbrayshaw wrote:

On 12/03/2016 10:59 a.m., Chuck Huber wrote:

 

Is there a flag associated with either a schematic or a board that would

indicate if changes have been made since the last save? Perhaps

something like:

 

    board(B) {

         if (B.isDirty) {

             ...

         }

    }

 

 

I didn't see anything in the ULP manual like this.

 

Thanks,

     - Chuck

 

Hi Chuck

 

No, the 'modified flag' is not made available via the ULP language.

If you don't want your ULP to run if changes have not been saved, you

will have to invert your thinking and have the ULP save first, every

time, and then re enter the ULP.

 

e.g.

run your ULP

 

if(argv(n) != obscureNumber) exit("write; run ULP obscureNumber;");

...the rest if your ULP

Good morning, Warren,

That's what I currently do.  Here's a bit more detail on what I'm

encountering.  Most of the time, a board file is not checked out of the

change management system (Perforce) and is thus not writable.  So when

the UPL tries to save, I get several pop-up dialog boxes indicating this

condition and offering to Save As...

I guess I could check the file mode on the file first, something like

(in bash parlance):

    && save the file

I don't see a ULP equivalent to lstat(2), so I guess this might be a job

for the system() function.

    if(argv(n) != obscureNumber && system("test -w myfile.brd") == 0) {

        exit("write; run ULP obscureNumber;");

    }

    ...the rest if your ULP

I use this in a context where additional instances of eagle are invoked

to generate gerber files.  Obviously these child instances are not aware

of changes that have been made to the board in the parent that have not

been saved.

Thanks,

    - Chuck

On 12/03/2016 10:59 a.m., Chuck Huber wrote:

 

Is there a flag associated with either a schematic or a board that would

indicate if changes have been made since the last save? Perhaps

something like:

 

    board(B) {

         if (B.isDirty) {

             ...

         }

    }

 

 

I didn't see anything in the ULP manual like this.

 

Thanks,

     - Chuck

Hi Chuck

No, the 'modified flag' is not made available via the ULP language.

If you don't want your ULP to run if changes have not been saved, you

will have to invert your thinking and have the ULP save first, every

time, and then re enter the ULP.

e.g.

run your ULP

if(argv(n) != obscureNumber) exit("write; run ULP obscureNumber;");

...the rest if your ULP

HTH

Warren