Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 1983
  • 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

hiShowProgressBar - unable to use...

ToMWUT

 Hello all,

 I have a very strange problem, I'm trying to use hiShowProgressBar function which is listed in a ui SKILL manual. I'm also able to find it via Finder. But when I try to execute this funcion I get such information:

*Error* eval: undefined function - hiShowProgressBar

My manual coresponds with 5.0 version of Cadence and I'm using 5.10 - so no problem here as well. I'm confused...

 ToM

 

  • It's an error in the documentation. The documentation was fixed in an IC5141 hotfix a couple of years ago, so it no longer refers to these functions.

    The functions  are only in ICOA5251 and IC61 onwards.

    Regards,

    Andrew.

  •  Andrew,

    I'm not very familliar with the versions... so is there any possibility for me to use this funcion or some replacement?

     My msfb version: 5.10.41.500.3.49

    Thanks,

    ToM

  • Well, the ProgressBox functions exist, just not the ProgressBar. They required the changes to Qt which happened in ICOA5251 (and further in IC61). Perhaps you can use those?

    Regards,

    Andrew.

  • I know Andrew about the hiDisplayProgressBox function and it would do the trick for me, but there is one problem. When I my application opens many ProgressBox'es one after another they are not closed. They are closed when the last ProgressBox closes.

    hiDisplayProgressBox(

    ?name s_name

    [?banner t_banner]

    [?text t_text]

    [?location l_location]

    [?callback g_callback]

    [?totalSteps x_totalSteps]

    [?delay x_delay]

    [?autoClose g_autoClose]

    )

    => t | nil

    And I'm setting the autoClose parameter to true. The problem remains even when I use different names for different ProgresBoxes.

    ToM

  • I found a similar report of this from a couple of years ago, and the workaround suggested then was to call  hiCancelProgressBox() when you're done with it. I just tried in the latest hotfix of IC5141 (5.10.41.500.6.136) and I can't reproduce the problem, so I think it's been solved now.

    Regards,

    Andrew.

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.