![]() With the CodeSMART Code View Assistant enabled, the Visual Basic code window dramatically changes with critical information provided on many control statements, branch lines to visually identify code nesting and assisted navigation between control statement opening and closing parts.īranch Lines are drawn to emphasize control statement branches, that is lines drawn between the opening and closing parts of each control statement very useful in visualizing code nesting.Įnd-of-Line Details represent descriptive comments at the end of certain control statement closing parts can be used to identify a long branch. The CodeSMART Code View Assistant brings a rich set of visual enhancements to the standard Visual Basic code editor window. Inject beauty into built-in VB6 core subsystems like the Object Browser and the Intellisense - the old, 16-color icons are gone and new, modern icons are now used, in line with CodeSMART's main subsystems. Tabbed MDI IDE: CodeSMART can change the Visual Basic standard multiple document interface (MDI) into a modern Tabbed MDI one similar to VS.NET and other modern environments. Tabs are added to the Immediate window, which is thus converted into a central reporting place while it does not loose its initial functionality.įull screen support: yes, it's true, you can code in VB6 while completely maximizing the work area! The lyt layout files distributed by the setup kit were not up-to-date.Īll the features it adds to Visual Basic are accessible through the main menu and four toolbars it registers with the environment.ĬodeSMART tools are hosted or display their results within dedicated tool windows that can be moved or docked.Ĭode view enhancements are displayed directly in the Visual Basic standard code editor window. Settings from previous versions of CodeSMART were not carried over to the new version. Links to registration were pointing to dead web pages. If a copy of CodeSMART 2009 for VB6 evaluation previously expired on the machine, then CodeSMART 2013 for VB6 was already expired at install time. If a node different than a component was double-clicked in the Project Explorer, the parent component node was not displayed in bold.Ĭlear Immediate Window did not work in demo setup kits. Initially set to off, we recommend setting it to on if you have enough processing power (enough would mean here a physical machine with an average but modern CPU). A glyph was drawn on some systems over public items' icon in the Project Explorer.Ī few users complained of slow editor updates, so a new setting was added in CVA "General" options: "aggressive refresh" (it controls how often the CVA gizmos are updated). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |