• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X PCB Editor
  3. Problem with scripts that require file browsers

Stats

  • Replies 11
  • Subscribers 159
  • Views 17365
  • Members are here 0
More Content

Problem with scripts that require file browsers

mikebystedt
mikebystedt over 11 years ago

Does anyone know of a workaround that would allow a script or axlShell() commands to select and populate a
file browser if it pops up?  It seems that the file browser form isn't recgonized.  So therefore no data can be entered.

Specifically, after doing a File->Import and running, a summary report pops up with the details.  When I select "Save",
a browser window pops up, but during Replay, the window is never selected, the filename never entered, and I can't
save the file.

I'm sure that someone else has encountered this at some point.  Any suggestions?

Is there some sort of default FORM name that I could refer to that isn't being output to the script file during a Record session?

Thanks, -Mike 

  • Cancel
  • Sign in to reply
Parents
  • mikebystedt
    mikebystedt over 11 years ago

    Thanks oldmouldy,

    But the problem I believe I'm looking at, is not so much that the "fillin value" needs to be dynamically tweaked,
    but that I can't actually get a handle to the browser window.  

    I'm actually attempting to record a script, then issuing the specific statements I want through
    axlShell() commands directly in a SKILL file.  I can't do a fillin whatsoever if I can't set the browser window to get
    ready to accept a value of any sort at all.  The method of sending out the commands, whether via a replay script
    or axlShell() calls, is just a programming decision.  However, neither method will work if I can't get a window handle
    for the "set window" command. Recording the script and reviewing, shows the "fillin" lines, but no window handle to set
    so that it can get the data loaded in correctly.

    So even the simplest of records and replays doesn't work if accessing the file browser is part of the equation.

    Is there some sort of standard handle for this sucker?  So that I can make the file browser the active window, and then
    do whatever I need to?  It's almost like the file browser window is completely invisible, although the commands thrown
    at it are still being recorded.

    Thanks,

    -Mike 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • mikebystedt
    mikebystedt over 11 years ago

    Thanks oldmouldy,

    But the problem I believe I'm looking at, is not so much that the "fillin value" needs to be dynamically tweaked,
    but that I can't actually get a handle to the browser window.  

    I'm actually attempting to record a script, then issuing the specific statements I want through
    axlShell() commands directly in a SKILL file.  I can't do a fillin whatsoever if I can't set the browser window to get
    ready to accept a value of any sort at all.  The method of sending out the commands, whether via a replay script
    or axlShell() calls, is just a programming decision.  However, neither method will work if I can't get a window handle
    for the "set window" command. Recording the script and reviewing, shows the "fillin" lines, but no window handle to set
    so that it can get the data loaded in correctly.

    So even the simplest of records and replays doesn't work if accessing the file browser is part of the equation.

    Is there some sort of standard handle for this sucker?  So that I can make the file browser the active window, and then
    do whatever I need to?  It's almost like the file browser window is completely invisible, although the commands thrown
    at it are still being recorded.

    Thanks,

    -Mike 

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information