1. General: Several CodeSMART subsystems were generating an unexpected behavior or were leading to a crash on projects containing 'Microsoft UserConnection' components.
2. General: An infinite loop occurred sometimes when CodeSMART was manually loaded after VB initialization and a project was also previously open with the active window being a designer.
3. Code Analyzer: A 'Type Mismatch' error was reported when performing a code analysis, related to unusual enum and type statement declarations.
4. Code Analyzer: Function parameters were incorrectly reported as 'dead code' if the method definition string had a certain construct (all parameters, including parentheses, were written underneath the line that has the function name on it).
5. Code Flow: Double-clicking on a method node did not move the cursor on the method's definition line.
6. Code Snippets: It was (incorrectly) possible for subfolders to be added as children of the 'Custom Code Items' folder.
7. Code View Assistant: Several grammar and code parsing problems were identified and corrected (related to unusual enum constructs, complex Input statements, etc).
8. Copy and Paste Buffers: An error was sometimes reported when trying to paste the empty contents of a multiple copy-and-paste buffer.
9. Project Explorer: Asking for a check-out operation using the corresponding menu entry in the CodeSMART Project Explorer tree was sometimes leading to checking-out a component different than the selected one.
10. Project Explorer: An error occurred in some cases when moving a component by drag-and-drop into an existing logical folder.
11. Project Explorer: Sometimes an error occurred on newly created projects when trying to create a new logical folder and to add components to it by using the 'Move Components' dialog.
12. Spelling Checker: An error was reported when trying to correct a misspelling on a read-only component.
13. SmartComplete: The smart complete list did not contain certain items if code was written starting at column 1.
14. Smart Copy and Paste: The subsystem did not operate correctly if the Visual Basic environment was in SDI mode.
15. Tracing: An error was reported while inserting tracing code at project group level.
1. General: On non-US keyboard layouts,
an overflow error was reported in some situations when editing code or changing
control properties through CodeSMART tools.
2. AutoText Manager: The splitter did not
save/restore its position between manager sessions.
3. Code Builders: An error was reported
when trying to insert a new property into an MDI form's code, when that
property also had a null default value.
4. Code Flow: ReDim instructions were not
represented in the 'Code Flow' tree as distinct “dimension instruction” nodes
when the subsystem was configured so.
5. Code Formatter: CodeSMART failed to
correctly format some code constructs (for instance: type declarations that
contain members named 'Type').
6. Code Formatter: Formatting a long code
line that was immediately followed by a multi-line comment block led sometimes
to a 'too many line continuations' error message.
7. Code Snippets: An error occurred when
refreshing the code snippet tree immediately after the selected code snippet
node had been deleted in another Visual Basic instance.
8. Code Snippets: A clipboard
malfunctioning message was sometimes reported when performing copy and paste
operations with code snippets.
9. Code View Assistant: There were
situations when the 'Code View Assistant' caused an excessively high memory
consumption which eventually led to out-of-memory errors.
10. Code View Assistant: CodeSMART failed to
add expected graphical enhancements into the code window due to internal
grammar minor inconsistencies.
11. Control Panel: It was possible to enter
incorrect values for some of the 'AutoSave' pane settings, which led to errors
being reported.
12. Error Handling: If no error handling
schemes were defined (i.e. when they were all deleted from the database) an
error was reported when opening the 'Edit Error Handling Schemes' dialog box.
13. Immediate Window: When docking the
'Immediate' window together with the 'CodeSMART Project Explorer' outside
Visual Basic's main window area, the 'Immediate' window tabs were not painted
any more.
14. Immediate Window: After moving the
'Immediate' window from docked state to a floating state, the tabs were not
painted until the window was resized.
15. Immediate Window: Several other docking
or graphical issues regarding the 'Immediate' window tabs were identified and
corrected.
16. Immediate Window: Trying to dock the
'Immediate' window immediately after performing a 'Code Analyzer' operation
yielded to an error being reported.
17. Project Explorer: 'MDI Form' and 'MDI
Child' component nodes had incorrect images in the 'CodeSMART Project
Explorer'.
18. Project Explorer: The SCC state for
shared components was improperly represented in the 'CodeSMART Project
Explorer'. This also led to the inability to perform correct SCC operations on
the corresponding components.
19. Project Explorer: Errors were reported
when trying to add an existing user control that had the same name as the
containing project.
20. Project Explorer: An infinite processing
loop was entered when trying to display the bookmark collection of a particular
method in the 'CodeSMART ‘Project Explorer', if there was a bookmark defined
before the last line of the respective method.
21. Smart Complete Manager: The splitter did
not save/restore its position between manager sessions.
22. Sort Procedures: Components containing
conditional compilation directives are now skipped by the sorting operation. A
better solution will be offered in the future.
23. Spelling Checker: Several errors
occurred when trying to use the spelling suggestions dialog box and the
corresponding 'Spelling' tab in the 'Immediate' window was not currently
selected.
24. Spelling Checker: An error was reported
when trying to use the spelling suggestions dialog box if all spelling checker
results were deleted from the result list.
25. Spelling Checker: Trying to perform a
spelling checker operation led to an infinite processing loop in situations
when the analysis had reached a complex code line that contained multiple array
assignment instructions separated by colons (“:”).
26. Spelling Checker: Sometimes the custom
dictionary file was overwritten when loading CodeSMART.
1. Code Formatter: The keyword items can
now be additionally moved in the corresponding list by using combinations
between Ctrl and the arrow keys.
2. Code Formatter: The maximum acceptable
length limit at which a code line can be wrapped was extended to 1024.
3. Custom Code: Indentation in the custom
code inserter is now configurable.
4. HotKey Designer: New option added to
the designer control’s context menu, which allows the user to automatically
pick a hotkey for the selected control.
1. General: A newer CodeMax20.ocx file
was included in the CodeSMART setup kit in order to avoid conflicts with
third-party programs that use commercial versions of this component.
2. General: Shared files (between
CodeSMART for VB6 and CodeSMART for VS.NET versions) are no longer stored in
the application installation folder, but in the “Program Files\Common
Files\AxTools Shared” folder.
3. General: On multiple monitor
configurations, the position of all CodeSMART progress windows was improperly
restored.
4. General: An error was reported by
CodeSMART at initialization when loading information about the (eventually)
active non-US keyboard layout character set.
5. General: Trying to close all open
components by using the Ctrl+F4 key combination sometimes lead to crashing the
VB6 environment.
6. General: Improper caret placement was
reported while writing a new method's declaration line.
7. General: An ‘Access Violation’ error
message occurred in some obscure circumstances when trying to undock windows in
the VB6 IDE.
8. Change Name and Text: An error was
reported when trying to access the Naming Standards Manager dialog directly
from the Change Name and Text wizard if this was done before editing the active
control’s Name and/or Text properties.
9. Code Analyzer: CodeSMART failed to
properly analyze optional parameters if they were initialized with array
elements or through method calls. Moreover, several errors were reported under
rare circumstances.
10. Code Formatter: When configuring the
'Blank Lines' formatting options, moving keywords in the corresponding list
generated selection problems if a keyword deletion operation was previously
performed.
11. Code Formatter: CodeSMART did not
properly format user-defined Type statements if they contained a field named
‘Type’.
12. Comments Remover: The dialog was
redesigned in order to also feature deleting all the CodeSMART specific comment
markers and modifiers.
13. Copy and Paste Buffers: In some obscure
circumstances the CodeSMART buffers failed to paste their content in code, also
reporting clipboard access errors.
14. Custom Code: Database nodes in the
"Custom Code" tree hierarchy could be edited, which further led to
cascading errors.
15. Full Screen: Dialog and toolwindow size
inconsistencies were reported when opening them in normal view mode if those
windows were previously opened in full screen mode and their “docked” status
was changed.
16. Naming Standards: "Naming
Standards" settings failed to properly initialize and in some situations
threw an error due to unavailable or altered database information.
17. Project Explorer: When working in
‘Logical View’ mode, the nodes sometimes lost their custom color when they were
moved in different folders by using drag and drop.
18. Project Explorer: When trying to
organize components in logical folders by using the Move Components wizard,
CodeSMART failed to load all project components if no logical folders were
previously defined.
19. Show Differences: Errors were reported
when searching for file differences in components that contained certain non-US
language characters.
20. SmartComplete: Several option and code
insertion inconsistencies were identified and corrected.
21. SmartComplete: Editing a smart complete
item in the SmartComplete Manager dialog and then saving the changes was
reported to alter the filter string by removing this one's last character.
1. General: CodeSMART document and
setting files are no longer stored by default in the application installation
folder, but in the "My Documents\My CodeSMART Files" (for document
files) and "Application Data\AxTools" (for setting files) folders.
This was mainly implemented as a fix to problems that appeared when running
CodeSMART on a restricted user account. Existing installations that function properly
will not be affected.
2. General: Some CodeSMART subsystems
like SmartComplete, Property Tips, Full Screen and dialog window positioning
failed to work correctly on multiple monitor configurations.
3. General: When working with different
keyboard layouts CodeSMART did not allow for language specific characters to be
entered in the code window if those characters had to be typed by using an
AltGr + Key combination.
4. General: An error was reported on
Windows 98 machines when trying to save a VB project before running it.
5. General: Various errors were reported
when loading CodeSMART due to the possibility of accessing other CodeSMART
features before the add-in was completely initialized.
6. General: Improved CodeSMART loading
time by 5-40% depending on software system configuration.
7. General: A one-time registry error was
reported by VB5 if the first start was on a restricted account.
8. Change Name and Text: CodeSMART can
now be instructed to rename all the controls in a control array if the user tries
to rename one control from that array by using the Change Name and Text tool.
9. Code Analyzer: This tool was reviewed
in order to fix various issues regarding memory leaks and inadequate memory
consumption ("Out of memory" errors were reported) which usually
occurred when analyzing large projects.
10. Code Explorer: Trying to refresh a
folder node led to an error when the folder was either an invalid logical
folder or it contained an invalid component.
11. Code Formatter: Single-line
"If…Then" instructions were incorrectly reformatted if their branches
contained at least two instructions separated by the “:” (colon) character.
12. Code View Assistant: Several grammar
errors were corrected (for instance, for single-line "ElseIf…Then"
and "While…Wend" statements).
13. Code View Assistant: Memory leaks were
found and fixed.
14. Control Panel: When changing the main
spelling checker dictionary to an inexistent or invalid language dictionary,
CodeSMART displayed the correct error message but then failed to reload the
previous dictionary.
15. Error Handling: In some situations an
error occurred while removing error handling code.
16. Find References: When a code line
contained two or more reference matches, only the first match was analyzed by
CodeSMART while the rest were ignored.
17. Find References: Performing a "Find
Variable References" search on an unformatted fully left-aligned method
could lead in some situations to Visual Basic stopping responding.
18. Full Screen: Having two or more Visual
Basic instances opened and extensively using the Full Screen feature could lead
in some situations to an initialization error when opening a new Visual Basic
instance.
19. HotKey Designer: An error was reported
when working with control captions that exceed 255 characters.
20. MDI Tabs: When performing a code
synchronization by using the correspondent toolbar button in the Project
Explorer window and pressing the arrow keys immediately after that, the MDI
tabs became empty.
21. Project Explorer: Some inconsistencies
were corrected regarding an invalid use of the reserved “[General]” section
node.
22. SmartComplete: On an unformatted code
line, the insertion of a smart complete item was preceded by a Visual Basic
line auto-formatting operation, leading to a misplacement of the cursor after
insertion.
23. SmartComplete: When compiling a project
by using a keyboard shortcut, the last selected SmartComplete item was
sometimes inserted into the active code window.
24. SmartComplete: The “ (quote) character
was not considered a SmartComplete insertion trigger.
25. SmartComplete: CodeSMART failed to
recognize certain SmartComplete insertion trigger keys other than Space and
Enter when working with non-US keyboard layouts.
26. SmartComplete: Insertion trigger
characters other than Space, Enter and Tab were lost in situations when the
SmartComplete item contained positional standard parameters (that is, begin/end
text selection "SB"/"SE” and cursor position "C”).
27. SmartComplete: An error was reported
when trying to save a zero-length SmartComplete item.
28. SmartComplete: The SmartComplete feature
could not be disabled by using the corresponding pane in the CodeSMART Control
Panel dialog box.
29. Sort Procedures: In rare circumstances
the ’Default’ attribute of a particular function was removed by the Sort
Procedures operation.
30. Task List: In rare circumstances a
‘Permission Denied’ error was reported when clicking on CodeSMART Task List
pane results.
31. Tracing: The tracing header string was
malformed when at least one method parameter was commented out but left as an
inline comment in the method definition line.
32. Workbench: An error was reported when
opening older projects due to a loading failure of the referred workbench
items.
1. General: CodeSMART now uses localized
fonts in the following subsystems: Code Explorer (including Workbench and
SearchList), Designer tools (Designer
Explorer, Tab Order, Change Name and Text, Hotkey Designer), Extended Find,
Find References, Code Snippets and Copy-and-Paste Buffers, Commenting tools,
Task List, etc. In addition to that, a dedicated pane is available in Control
Panel for configuring the Charset value that must be used in the corresponding
CodeSMART windows.
2. Change Name and Text: The dialog
window initializes the Text/Caption text box with the corresponding control’s
font. Especially useful on non-US systems.
3. Control Panel: New pane available for
configuring and optimizing window positions for all CodeSMART dialogs. Multiple
monitor configurations are fully supported.
4. Extended Find: The Extended Find
dialog initializes the "Search For" combo box with the active word
string when no selection is made in the code window.
1. General: On certain occasions, an
error was reported while loading projects on systems that had no Source Code
Control tool installed.
2. General: Several grammar errors were
corrected.
3. General: The Visual Basic 5.0 IDE hung
on startup when CodeSMART was set to load.
4. Error Handling: Cascading errors were
reported in some unusual situations when a line numbering operation was
performed on a read-only component.
5. Find References: Trying to access the
‘Find References’ entry from a property node in Project Explorer contextual
menu led to an empty results list due to an incorrect initialization of the
find references object.
6. Full Screen: An error was repeatedly
reported when working with the Full Screen feature due to an internal failure
in the Visual Basic IDE.
7. Project Explorer: On certain
occasions, CodeSMART did not load all project components in the Move Components
wizard dialog, especially when the active project contained components of
‘Related documents’ type.
8. SmartComplete: Trying to access
any CodeSMART feature while the SmartComplete window was still visible caused
errors.
9. SmartComplete: Some of the VBA
string functions, like Mid$, Replace$, etc, were not correctly inserted in code
when the cursor position was not at the end of the entered word or the user had
entered the full word including the $ character before selecting the
SmartComplete item from the list.
10. SmartComplete: The SmartComplete
item list was not properly filtered according with the current settings when
loading the SmartComplete Manager dialog.
11. SmartComplete: Several errors
related to a window accessibility were reported when working with the
SmartComplete feature.
12. Tab Order: In some occasions it was
possible to access the ‘Move Up’ command for the first element in the designer
control list.
1. Standard Parameters: The (ParamList}
standard parameter is now supported by various CodeSMART subsystems, like
AutoText, SmartComplete, Code Snippets, Error Handling, etc.
1. General: Several grammar problems were
corrected, implicitly improving certain CodeSMART subsystems. Some of the newly
supported code constructs are: method parameters whose names are identical to
VB keywords, file operation statements that use complex expressions for the
file number parameter, enum items declared with brackets and used accordingly
as a method parameter, etc.
2. General: On certain systems, an error
related to the Gif89.dll library occurred when trying to open the
'SmartComplete Manager' and 'AutoText Manager'.
3. General: An error was reported on
Windows 9x systems indicating a failure in the Code View Assistant feature
loading process.
4. AutoText: The AutoText feature could
not be disabled by using the corresponding option in the CodeSMART Control
Panel.
5. AutoText: On some systems, the use of
the Ctrl+Space key combination as AutoText trigger led to a significantly
slowness in the activation of the Visual Basic Intellisense window.
6. Bookmarks: An error was reported under
rare circumstances when performing a control statement bookmarks insertion. The
error was caused by an unusual code construct.
7. Change Name & Text: An error was
reported when performing a naming standards setting change directly from the
Change Name & Text dialog, if immediately followed by editing the Caption
text box.
8. Code View Assistant: When using complex
statement blocks (for example, multiply nested If…End If and For…Next
statements) the end-of-line details were incorrectly displayed on some of the
corresponding branches.
9. Code View Assistant: All of Code View
Assistant's features are now disabled while Visual Basic is in run mode.
10. Code View Assistant: For some unusual
code constructs – like a Do…Loop statement that has no condition at all – the
CodeSMART code parser engine was unable to correctly parse the code.
11. Commenting Tools: In some rare
occasions, auto-insertion of method header comments was not performed or had
incorrect values for some of the CodeSMART standard parameters.
12. HotKey Designer: A “Subscript out of
range” error was reported when generating hotkeys, due to the complexity of
certain designers.
13. Project Explorer: Right-clicking a
module in the Project Explorer and choosing 'Open Containing Folder' option
correctly opened the folder, but it was followed by a CodeSMART message about
the module file not being found.
14. SmartComplete: If the right hand
indicator bar is set to be shown, horizontally scrolling the code window now
hides the indicator bar until the scroll bar is back to its original leftmost
position.
15. SmartComplete: An error occurred
when trying to access any CodeSMART commandbar or toolbar button while the
SmartComplete window was still active.
16. SQL String: A field qualified with the
containing table name was truncated to the table name when placed in the Order By
clause of a Select statement.
17. Tab Order Designer: An error occurred
when either label controls or controls with the TabStop property set to false
were filtered out, and the tab order was rearranged by using the corresponding
command buttons.
1. SmartComplete: New SmartComplete
items were included in the database.
2. Tab Order Designer: An additional icon
was added for each designer control in the Tab Order Designer dialog box,
specifying that the corresponding control is out of the correct order that
would have been established by the AutoOrder.