PROGRESS BAR Sample Clauses

PROGRESS BAR. The progress bar (CW_PROGRESS_BAR) is a central element along with the user interaction. It gives the user feedback about a started process and also gives him an idea of how much time the operation will take. Figure 10 shows a screenshot of the progress dialog. The wizard uses the progress dialog when it: • parses the .NET assembly • reads the XML file containing the proxy classes’ representation • backs up the files in the project directory • generates the Eiffel proxy classes, the Ace and XML files • checks the syntax of the generated Eiffel files • compiles the classes to a new .NET assembly • does finish freezing • restores files from the project directory Every class that wants to indicate a progress inherits from the class CW_GUI_SUPPORT that provides an access point to the progress dialog called Progress_dialog. In order that every class accesses the same instance of the dialog, Progress_dialog is a once feature. A once feature executes its body only the first time it is called in a system execution. The result obtained by the first call is applicable to all instances of a class.
AutoNDA by SimpleDocs

Related to PROGRESS BAR

  • PROGRESS EVALUATION Engineer shall, from time to time during the progress of the Engineering Services, confer with County at County’s election. Engineer shall prepare and present such information as may be pertinent and necessary, or as may be reasonably requested by County, in order for County to evaluate features of the Engineering Services. At the request of County or Engineer, conferences shall be provided at Engineer's office, the offices of County, or at other locations designated by County. When requested by County, such conferences shall also include evaluation of the Engineering Services. County may, from time to time, require Engineer to appear and provide information to the Williamson County Commissioners Court. Should County determine that the progress in Engineering Services does not satisfy an applicable Work Authorization or any Supplemental Work Authorization related thereto, then County shall review same with Engineer to determine corrective action required. Engineer shall promptly advise County in writing of events which have or may have a significant impact upon the progress of the Engineering Services, including but not limited to the following: A. Problems, delays, adverse conditions which may materially affect the ability to meet the objectives of an applicable Work Authorization or any Supplemental Work Authorization related thereto, or preclude the attainment of Project Engineering Services units by established time periods; and such disclosure shall be accompanied by statement of actions taken or contemplated, and County assistance needed to resolve the situation, if any; and B. Favorable developments or events which enable meeting goals sooner than anticipated in relation to an applicable Work Authorization’s or any Supplemental Work Authorization related thereto.

  • Progress Update Information included with the annual Data Access Request (DAR) renewal or Closeout summarizing the analysis of controlled-access datasets obtained through the DAR and any publications and presentations derived from the work.

  • Wage Progression Employees within their position classification will progress from the “start rate” to the “one year rate” and so on, on the basis of 1,800 hours worked at the “start rate” to the “one year rate” and so on. Hours worked and paid for, including hours paid during the probationary period (450) hours, and hours not worked and paid for by the WSIB shall be considered hours worked for the purposes of computing eligibility to progress to the next higher rate within their position classification.

  • PROGRESS AND COMPLETION 8.2.1 All time limits stated in the Contract Documents are material terms and time is the essence of the Contract. A failure by Contractor to do what is required by the time specified in the Contract Documents is a breach of the contract. 8.2.2 The Contractor shall begin the Work on the date of commencement as defined in 8.2.3 If in the sole opinion of the State, the Contractor fails to commence work on the project or to complete the work of said project within the time specified above, or to prosecute the work in such a manner that it appears that the completion date can be assured, the State shall have the right to notify the Contractor by Certified Mail that the terms of the Contract have been violated, and that effective immediately the Contract is terminated and the State has the right to and in fact is taking over and attending to completion of the project without prejudice to the State's remedies for any losses sustained

  • Progression For progression for all classifications under this agreement, refer to Schedules A to D.

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • PROGRESS SCHEDULE The Contractor, within ten (10) working days of receiving notice of the award of the contract, shall prepare and submit for the State's and Architect's information an estimated progress schedule for the Work. The progress schedule shall be related to the entire Project to the extent required by the Contract Documents, and shall provide for expeditious and practicable execution of the Work.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!