Stats

  • Locked Locked
  • Replies 10
  • Subscribers 143
  • Views 17548
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Create a print out log GUI

psill000

My script has some print outs and is there a way to create a print out log GUI of those print outs.

The closest thing I could find is the  hiCreateMLTextField, but I would have to append every string to the current value. Also, I dont know how clear it may become in reading previous and if the string would become too big and cause problems.

It is not that big of an issue to append the string, just looking for the most effective way to have a print out log GUI.

The print out would be strictly used for reading print output. I know I can print to the CIW, but some users want a print out GUI.

Paul

Parents
  • Andrew Beckett

    You could just use a sensibly named global variable to hold the windowId. If you have an aversion to global variables for such things, then you could always use some lexical scoping using the SKILL++ (Scheme) features:

    let((windowId)
      globalProc(CCFcreateTextWindow(@rest args)
        windowId=apply(hiCreateWindow args)
      )
      globalProc(CCFgetTextWindow()
        windowp(windowId) && windowId
      )
    )

    Then you can create a window using:

      CCFcreateTextWindow(nil "text" "Show File")

    and later refer to the ID using:

      CCFgetTextWindow()

    The file above needs to be put in a file with a ".ils" suffix. It will also only work from IC615 onwards because it uses globalProc. It could be implemented in earlier releases by doing:

    let((windowId)
      CCFcreateTextWindow=lambda((@rest args)
        windowId=apply(hiCreateWindow args)
      )
      CCFgetTextWindow=lambda(()
        windowp(windowId) && windowId
      )
    )

    No global variables were harmed in the implementation of this code.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    You could just use a sensibly named global variable to hold the windowId. If you have an aversion to global variables for such things, then you could always use some lexical scoping using the SKILL++ (Scheme) features:

    let((windowId)
      globalProc(CCFcreateTextWindow(@rest args)
        windowId=apply(hiCreateWindow args)
      )
      globalProc(CCFgetTextWindow()
        windowp(windowId) && windowId
      )
    )

    Then you can create a window using:

      CCFcreateTextWindow(nil "text" "Show File")

    and later refer to the ID using:

      CCFgetTextWindow()

    The file above needs to be put in a file with a ".ils" suffix. It will also only work from IC615 onwards because it uses globalProc. It could be implemented in earlier releases by doing:

    let((windowId)
      CCFcreateTextWindow=lambda((@rest args)
        windowId=apply(hiCreateWindow args)
      )
      CCFgetTextWindow=lambda(()
        windowp(windowId) && windowId
      )
    )

    No global variables were harmed in the implementation of this code.

    Regards,

    Andrew.

Children
No Data

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.