Any suggestions on the best way to create a progress bar in SKILL? I thought I would resize a form field as a progress bar (see below), however it is not visible during execution. --- Erik procedure(pbform() prog(() ff_list=list( list( hiCreateLabel( ?name 'pb_message ?labelText "msg1" ) (0:10) (0:10) ) ; list list( hiCreateStringField( ?name 'pb ?prompt "" ?editable nil ) (0:30) (20:10) 0 ) ; list ) ; list hiCreateAppForm( ?name 'pb_form ?formTitle "progress bar" ?fields ff_list ?dontBlock t ) ;display form hiDisplayForm(pb_form) return(t) ) ) pbform() for(i 1 200 dprint(i) ) pb_form->pb_message->value="msg2" hiResizeField(pb_form 'pb (50:30))
(Erik Wanta) asked: I sent Erik (to his corporate address) the gist of PCR 607074 which I filed 07-24-2003 basically asking for a DFII progress bar when loading any sizeable (millions of transistors) layout cellview. Basically, I load our large 10-million Raptor SoC all the time into DFII and I myself (and others) would like to see just such a DFII progress bar. In that PCR, the central architecture group discusses an existing HI progress-bar widget which may be of use to you today. Also discussed are a variety of methods to determine 'progress', e.g., - store the last-load time & compare against that previous time - compare amount of data on disk vs amount of data loaded to VM - peruse hierarchy based on pc.db for the total-time calculations - etc. Any ideas, please post to the NG so I can append them to the PCR.
Turns out IC440 had a progress bar SKILL program (thanks to sleuthing by Andrew Beckett who located the source code for same). Meanwhile, the framework guys are building new progress-bar widgets as we speak (PCR 607074). So, it seems best to offer support for the existing forms-based method, until/unless the specialty widget arrives on the scene. To that end, I opened a service-request ticket (32530684) for our friend Erik to get what he needs (either by supporting the code Erik has written and supplied or by providing aource to the existing progress-bar SKILL if that src SKILL is usable, public, linted, capitalized, etc.).