Actions
Forum Thread Details
  • Replies 4 replies
  • Subscribers 175 subscribers
  • Views 508 views
  • Users 0 members are here
Related

local/user information in a ULP?

mr.chris.styles

HI All,

 

I have scanned the extensive ULP documentation, i could well have missed it, but I have not been able to find any way for a ULP to access information about Eagle revision number, registered user, serial number, etc etc.

 

I'm doing some experiments with ULPs, never written them before, and the ability to understand who exactly is running the ULP would be pretty useful!

 

Any hints/tips appreciated..

 

Cheers,
Chris

Parents

  • Hi Chris,

     

    an ULP does not have registration information accessible, but you have

    access to EAGLE's version numbers through some predefined constants.

    You'll find these constants in the HELP under "User Language" ->

    "Builtins" -> "Builtin Constants", for example:

     

    string s;

    sprintf(s, "%d.%d", EAGLE_VERSION, EAGLE_RELEASE);

    dlgMessageBox(s);

     

    dlgMessageBox(EAGLE_SIGNATURE);

     

     

    Rene

     

     

  • in reply to autodeskguest

    Thanks for the rapid reply!

     

    Too bad I can't get at the serial number, as that would uniquely identify the installation, while maintaining anonymity...

     

    While I am here, are there any plans to add "version" properties to sch, brd and library files? Another built in variable that can be set/seen in the UI, or munged directly in the XML if needed?

     

    im really interested in starting a trial with cadlab.io ... looks like we're thinking along similar lines...

     

    Cheers,

    Chris

  • in reply to mr.chris.styles

    Am 22.12.2016 um 20:24 schrieb Chris Styles:

    While I am here, are there any plans to add "version" properties to sch, brd and library files? Another built in variable that can be set/seen in the UI, or munged directly in the XML if needed?

     

    Not for the library, but for the schematic and board you can add such

    information right now, through global ATTRIBUTEs. But keep in mind that

    global ATTRIBUTEs aren't really global - they are local to the drawing

    you're editing. An ATTRIBUTE added to the schematic is not visible in

    the board and vice versa.

     

    Rene

     

     

Reply
  • in reply to mr.chris.styles

    Am 22.12.2016 um 20:24 schrieb Chris Styles:

    While I am here, are there any plans to add "version" properties to sch, brd and library files? Another built in variable that can be set/seen in the UI, or munged directly in the XML if needed?

     

    Not for the library, but for the schematic and board you can add such

    information right now, through global ATTRIBUTEs. But keep in mind that

    global ATTRIBUTEs aren't really global - they are local to the drawing

    you're editing. An ATTRIBUTE added to the schematic is not visible in

    the board and vice versa.

     

    Rene

     

     

Children
No Data