The widget displays an arrow in the left margin, marking the code line that is being executed. The code widget shows the code of the currently selected script. While typing, you can press the TAB key to get possible completions for the expression. The expression will be evaluated in the associated stack frame. Double-click on the value and type in the new value the value can be an arbitrary expression. Properties that are not read-only can be edited. Properties whose value has changed are shown in bold font. Objects can be expanded, so that their properties can be examined, recursively. The locals widget shows the variables that are local to the currently selected stack frame that is, the properties of the objects in the scope chain and the this-object. To select a particular stack frame to inspect, click on its row. A row contains the frame index (0 being the inner-most frame), the name of the script function, and the location (file name and line number). Each row represents one frame in the stack. The stack widget shows a backtrace of the script execution state. Typing "x = 123" will assign the value 123 to the variable x in the current scope (or create a global variable x if there isn't one - scripts evaluated through the console can have arbitrary side effects, so be careful). For example, typing "x" and hitting enter will evaluate "x" in the current stack frame and display the result. The console provides a simple and powerful way of manipulating the script environment. Commands and script variables are auto-completed through the TAB key.Īny console command that causes a change in the debugger or debugger target's state will immediately be reflected in the other debugger components (e.g. The set of commands and their syntax is inspired by GDB, the GNU Debugger. The console widget provides a command-line interface to the debugger's functionality, and also serves as an interactive script interpreter. The following table describes each component and how they relate to each other. The debugger's functionality is divided into a series of components, each being a widget that can be shown in the main window of the debugger. It will be invoked again if one of the conditions described in the list above is met. The debugger will resume, i.e., give the control back to the script engine, when the user clicks Continue menu item from the Debug menu. Once the debugger is started, the execution state can be inspected, e.g., the value of variables can be queried and the current program stack shown. An uncaught script exception is thrown.Clicking the Interrupt menu item from the Debug menu in the main window.The debugger statement is encountered in the script.The debugger will start, i.e., take control over the script's execution when any of these conditions are met: The following image shows the debugger as created with standardWindow(): We assume that the debugger has been integrated into the application through the QScriptEngineDebugger::standardWindow() function, which provides the standard debugger configuration. We assume that the reader is somewhat familiar with general debugging concepts and existing debugging tools. This manual describes how to use the debugger. Application developers can embed the debugger into their application through the QScriptEngineDebugger class. It does not store any personal data.The Qt Script Tools module provides a debugger for script execution in Qt applications that use Qt Script. The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |