📄 revisionhistory.htm
字号:
<tr>
<td>WrapColAutoCountMax = 3 (for Vertical Legends) or WrapColAutoCountMax
= 100 (for Horizontal Legends)</td>
</tr>
<tr>
<td>WrapColSpacingMin = 2</td>
</tr>
<tr>
<td>WrapColSpacingAuto = True</td>
</tr>
<tr>
<td>WrapRowDesiredCount = 1</td>
</tr>
<tr>
<td>WrapRowAutoCountEnabled = True</td>
</tr>
<tr>
<td>WrapRowAutoCountMax = 100 (for Vertical Legends) or WrapRowAutoCountMax
= 5 (for Horizontal Legends)</td>
</tr>
<tr>
<td>WrapRowSpacingMin = 0.25</td>
</tr>
<tr>
<td>WrapRowSpacingAuto = True</td>
</tr>
</table>
</li>
<li>Added new OPC event handler to all OPC-enabled components: OnBeforeNewOPCData.
This event passes the index of the OPC item and the variant data value by reference
(pointer reference) so that you can modify or scale the value before it is passed
to the component and before the standard event handlers are called.</li>
<li>Added independent Cursor and Legend data point value formatting to the Plot
Pack axis objects. Each channel is associated with a Y-Axis and X-Axis.
Each axis is responsible for specifying the formatting of displayed data for values
associated for that axis. This goes for channel data displayed in other
objects, such as in the cursor and/or legend objects. By default, all objects
display X and Y values formatted as shown in the respective axis. For example,
if the X-Axis is formatted as date/time "hh:nn:ss", then X-values displayed in
the Data Cursor are displayed formatted the same way. You can now override
this default formatting, and specify that the formatting be different when displayed
in either the Legend or Data Cursor Objects. The following new properties in the
X and Y-Axis objects...<br>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" id="AutoNumber3">
<tr>
<td><b>CursorUseDefaultFormat</b> </td>
</tr>
<tr>
<td><b>CursorFormatStyle</b> </td>
</tr>
<tr>
<td><b>CursorDateTimeFormat</b></td>
</tr>
<tr>
<td><b>CursorPrecisionStyle</b> </td>
</tr>
<tr>
<td><b>CursorPrecision</b> </td>
</tr>
<tr>
<td><b>CursorMinLength</b> </td>
</tr>
<tr>
<td><b>CursorMinLengthAutoAdjust</b></td>
</tr>
<tr>
<td><b>LegendUseDefaultFormat</b> </td>
</tr>
<tr>
<td><b>LegendFormatStyle</b> </td>
</tr>
<tr>
<td><b>LegendDateTimeFormat</b> </td>
</tr>
<tr>
<td><b>LegendPrecisionStyle</b> </td>
</tr>
<tr>
<td><b>LegendPrecision</b> </td>
</tr>
<tr>
<td><b>LegendMinLength</b> </td>
</tr>
<tr>
<td><b>LegendMinLengthAutoAdjust</b></td>
</tr>
</table>
<p>The following properties serve as the "Default Formatting" for the Legend and
Cursor Objects when the UseDefaultFormat properties are set to TRUE...</p>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" id="AutoNumber4">
<tr>
<td>LabelsPrecision </td>
</tr>
<tr>
<td>LabelsPrecisionStyle </td>
</tr>
<tr>
<td>LabelsFormatStyle </td>
</tr>
<tr>
<td>DateTimeFormat </td>
</tr>
<tr>
<td>LabelsMinLength </td>
</tr>
<tr>
<td>LabelsMinLengthAutoAdjust</td>
</tr>
</table>
</li>
<li>Updated installer to support Delphi 7 VCL and CLX components.</li>
<li>Upgraded Plot Pack to correctly display long labels in the X and Y-axes so
that they are not "cropped" when near the edge of the component. This has
resulted in a change in the layout of the plot component objects, particularly
the Legend and Label objects. Now, the Label object and Legend object top/bottom/left/right
margin properties are strictly interpreted. This will result in the gap
between the Legend and the Data View as well as Labels and the Data View shrinking
to be exactly the margin specified by the top/bottom/left/right margin properties.
<br>
<br>
Since the default top/bottom/left/right margins for the Legend are set at a default
of one character, the margin between the Data View and the Legend will now be
exactly one character. Since the default top/bottom/left/right margins for
the Label is set at a default of zero characters, the margin between the Data
View and the label will now be exactly 0 characters (plus font specific kerning).
This means that with most fonts, there will be a kerning gap (extra space added
below the baseline to accommodate characters that are generally drawn below the
baseline such as "j" or "g"), but letters that go below the kerning baseline
will now touch the Data View. To fix this, we recommend setting the margin
nearest the Data View to 0.25 characters (or alternatively setting all margins
for all labels to 0.25 characters). This change should not affect most users
in a negative way, but will slightly change the visual layout of some objects.</li>
<li>iObjectCanvas now supports loading images into a built-in image list that
can also stream into your form. You can also load image lists from resources
using name or ID.</li>
<li>Added GetDisplayXToPixelsX and GetDisplayYToPixelsY to iObjectCanvas.
Allows conversion between the component's display units and pixels on the component.</li>
<li>Added new iImageDisplay component. Allows loading of multiple bitmap
frames, and controllable animation framerate.</li>
<li>Updated Plot Pack component backgrounds to support gradient colors.</li>
<li>Added new iPipe component. Includes 3d straight pipe and animation capabilities.</li>
<li>Added new iPipeJoint component. To be used with the iPipe component.</li>
<li>Added new iIntegerOutput component. Similar to iAnalogOutput, but supports
Integer only output. Supports Integer, Hex, Binary, and Octal formatting
styles.</li>
<li>Added new iScope Component. True Analog/Digital Oscilloscope component
with built-in Trigger.</li>
<li>New VCL/CLX, ActiveX WinHelp, and ActiveX HTML Help for MSDN (Pre January
2002 Editioin) Files including many corrections.</li>
<li>Added new iLCDMatrix component. Includes 5x7 built-in character font
for displaying 5x7 dot-matrix display text. Also supports loading
external character sets of custom size. Several additional 5x8 character
sets are included. An external font editor is available for download from
our website.</li>
<li>Added new iMotor component.</li>
</ol>
<p></p>
<hr size="1" color="#C0C0C0">
<h4>ActiveX and VCL/CLX Version 2.1.2 Service Pack 6</h4>
<h4>Bug Fixes:</h4>
<ol>
<li>Fixed "Interface Not Supported" exception in Visual Basic.NET and C#.NET that
occurred with the Plot Pack. </li>
<li>Fixed problem where popup dialogs and runtime property editors would block
other threads from accessing the component while they were visible. Unnecessary
Lock and Unlocks by these dialogs were removed.</li>
<li>Redesigned the Iocomp Theme Panel component in the Iocomp Design-Time property
editors to fix a bug under Windows 95/98/ME operating systems when applying changes.
Nested panel components within the theme panel were causing conflicts with the
Windows API combo boxes that were used.</li>
<li>Redesigned the Iocomp Theme Panel auto-centering code for compatibility under
CLX.</li>
<li>Fixed bug in iModeComboBox VCL component where the OnChange and OnChangeUser
events would not fire under Delphi 4-5 and C++ Builder 4-5.</li>
<li>Fixed bug in Plot Pack Annotations when used with logarithmic axes.
The annotation would size logarithmically instead of linearly when doing manual
sizing with the mouse at runtime.</li>
<li>Fixed ActiveX compatibility issues with Microsoft Visual Studio.NET.
Components now successfully stream and function with managed VB.NET and C#.NET
applications. ActiveX components already were compatible with Visual C++.NET.
See the Iocomp ActiveX Release Notes for any issues with porting older Visual
Basic 5/6 applications to VB.NET using our ActiveX components.</li>
<li>Fixed absolute positioning bug in Internet Explorer. Component would
always be positioned at the origin (upper left-hand corner) of the web page if
absolute positioning was used with our components.</li>
<li>Fixed misspelling for default filename in the Plot Pack Save JPEG/BITMAP/Metafile
dialog.</li>
<li>Limited DateTime format dates to years between 1400 to 9000. This resolves
zooming errors that occurred when trying to zoom past these limits.</li>
<li>Fixed multiple pointer streaming issue in the ActiveX Gauge Components.
If multiple pointers were setup at Design-Time, they would not be streamed correctly
to the form. </li>
<li>Fixed problem with Plot Pack zooming when using Logarithmic scales.</li>
<li>Fixed Plot Pack Differential Interpolation drawing algorithm problem.
The last data point should draw to infinity. If the last data point went
out of view, the infinity line would incorrectly disappear.</li>
<li>Fixed problem where an additional pointer would be added to our gauge components
every time you loaded the project in Visual Basic.</li>
<li>Fixed Theme problem where width and height of preview component would be switched
if the orientation of the component was opposite of the default setting.</li>
<li>Fixed GetBytes JPEG memory leak and speed issues.</li>
<li>Fixed recursive painting bug when using stacked axes in the Plot Pack.
This only became obvious with large, viewable data sets.</li>
<li>Fixed OPCItem browser limitation of 256 computers when browsing a Windows
computer domain. The limit has been upgraded to support approximately 1000
computers per domain when browsing.</li>
<li>Fixed bug during development under Windows 95a/b where the component would
appear to be unlicensed. This did not affect deployed applications under
Windows 95a/b, only development.</li>
<li>Fixed runtime property editor bug with plot pack when running under large
fonts. Form would not automatically scale properly to large fonts.</li>
<li>Fixed memory leak in iKeyboard drawing algorithm.</li>
<li>Corrected ActiveX sizing problem in RSView.</li>
<li>Fixed iObjectCanvas OnClickObject event. The event handler was not firing
correctly.</li>
</ol>
<h4>New Features:</h4>
<ol>
<li>Added to iPlotChannelCustom, DrawStartIndex and DrawStopIndex that inform
you of the data point indexes that are currently visible in the Data View.</li>
<li>Added OnBeforeLoadProperties and OnAfterLoadProperties events added to Plot
Pack Components.</li>
<li>Added Width, Height, Left, and Top properties for ActiveX containers that
do not provide these properties by default. These properties are specified
in pixels. If the container overrides these properties then the container
will be responsible for these properties. For example, Visual Basic overrides
these properties and replaces them with its own container properties. Its
container properties are specified in Twips by default and not in Pixels.</li>
<li>Added UserCanAddRemoveChannels property. This property controls whether
the Add/Remove buttons are shown in the Runtime Property Editor.</li>
<li>Added SaveAnnotationsToFile and LoadAnnotationsFromFile methods to the Plot
Pack Components. This method should be called after loading properties from
a file since the loading of properties clears out the entire control.</li>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -