STINGRAY STUDIO 12.

1 RELEASE NOTES
Stingray Studio

ROGUE WAVE SOFTWARE / WWW.ROGUEWAVE.COM

 Introduction

In this Document
These release notes contain a summary of new features and enhancements, late-breaking product
issues, migration from earlier releases, and bug fixes.

For change logs or other information on previous releases, please contact Technical Support.

NOTE >>
Rogue Wave products may contain undocumented interfaces. These interfaces are not
supported for general use and may be changed or removed from release to release.

NOTE >>
The version of this document in the product distribution is a snapshot at the time the product
distribution was created. Additional information may be added after that time because of
issues found during distribution testing or after the product is released. To be sure you have
the most up-to-date information, see the version of this document on the Rogue Wave web
site:
http://www.roguewave.com/help-support/documentation/stingray

ROGUEWAVE.COM 3
 New Features

Updated Platform Support

Please see the Supported Platforms at http://www.roguewave.com/products-
services/stingray. Select the supported platforms link.

In this release, we have removed all MSVS 2010 solutions, projects, etc. However, all documentation,
other than this document, have not been updated with this change.

Note that this version supports the latest Visual Studio 2015 as well as Windows 10, in 32 or 64 bits.

New Implementation for Read-Write Excel Files in Grid

The GridExcelHelper library supports reading and writing Excel files in .xlsx format in C++ Grid
projects. The library is based on Office Open XML SDK and requires Common Language Runtime (/clr)
support to be enabled. See Objective Grid Users Guide: PART II Programmers Guide: Chapter 26 Excel
Data Exchange Support.

Objective Grid for Microsoft .NET

Implementation language update

Previous versions of the Grid control in .NET were written in Managed C++, a programming
language no longer supported by Microsoft. This release provides the same component,
rewritten in C++/CLI, the .NET-compliant implementation of C++.

Project configurations

All library and sample projects in Objective Grid for .Net are provided with Debug and Release
configurations for both 32-bit and 64-bit platforms.

ROGUEWAVE.COM 4
 Objective Grid for Microsoft .NET has been tested with .NET Framework 4.5.2, 4.6, and 4.6.2

The default .NET framework selected by Visual Studio 2015 is 4.6.

However, the Objective Grid for Microsoft .NET component still ships for older versions of
Visual Studio, so all the project files for Objective Grid for Microsoft .NET target the oldest
supported .NET framework at the time of this writing: 4.5.2.

If you plan to deploy the component on platforms that have only the .NET Framework 4.6, make
sure the project files are updated accordingly.

To target a later version of the .NET Framework, the following changes are needed:
o Open the GridControl and GridHostNet project files (GridControl*.vcxproj and
GridHostNet*.vcxproj) in a text editor. In the section <PropertyGroup Label="Globals">,
the following line should be changed, replacing 4.5.2 with the required version:
<TargetFrameworkVersion>v4.5.2</TargetFrameworkVersion>

o In the GridUtils, GridTabControl and GridExcelHelper projects, the target framework

should be set on the Application page of the project's properties in Visual Studio.

API changes
o Every exposed API that uses or returns a row or column index now uses an unsigned
integer (the System.UInt32 .NET type) instead of a signed integer. Including the
GridControl class and its dependent classes (such as all the event handler classes).
When compiling your code, you may notice signed/unsigned warnings that should be
fixed by using the appropriate type for row and column indices (uint in C#, UInteger
in Visual Basic).
o The GridControl.AcclerateArrowKey property was renamed to
GridControl.AccelerateArrowKey. The legacy name is preserved for backward
compatibility.
o The GridControl.AcclerateScrollBars property was renamed to GridControl.
AccelerateScrollBars. The legacy name is preserved for backward compatibility.
o The GridControl.NavigateInGrid property was added to allow switch from default
navigation with keyboard keys inside the grid to navigation between the grid and other
controls on a form.

Known Issues

o Under Visual Studio 2015 U1 for both Win32 and x64 builds, running the debug
configuration of the EventHandlingByInheritance sample produces the
message, "You are debugging a Release build of DerivedGridControl.dll".

ROGUEWAVE.COM 5
 This issue appears to be related to a Microsoft bug in VS 2015 U1:
https://connect.microsoft.com/VisualStudio/feedback/details/2116788/flag-optimize-is-
passed-to-the-debugger-even-while-the-build-settings-optimize-code-is-not-enabled-on-
mvc-c-web-projects-when-using-just-my-code

To avoid this problem, under Debug->Options check the option Suppress JIT optimization
on module load (Managed only).

o Because of changes in properties attributes and the designer, some code generated by
old versions of the designer may be obsolete and are not generated by the new
designer. If these statements cause any problem, they should be manually edited or
deleted.

For example, in the ExcelLike sample, in the file GridDocuments.cs, under:

#region Windows Form Designer generated code

we removed statements like:

this.gridControl1.GridDesignerCell(1,2).Style.ValidMaximum = "0";

These statements caused misbehavior in the sample.

o Hierarchical Grid functionality is not supported in this release.

ROGUEWAVE.COM 6
 Bug Fixes

Build Wizards
Foundation Build Wizard now creates Foundation12.mak. [SRSTUDIO-4947]

Objective Toolkit
Fixed 64-bit pointer truncation problem in SECTreeCtrl::SortChildren() and
SECTreeCtrl::SortChildrenCB(). [SRSTUDIO-2834]
Fixed SECListBoxDirEditor to launch SECDirSelectDlg as a modal dialog. It was a modeless
dialog, which could lead to crashes in some cases. [SRSTUDIO-3931]
Removed unnecessary dependency on ScriptHost.tlb. When ActiveScript was excluded in
the Objective Toolkit Build Wizard, there was still a dependency in ScriptHost.rc which caused
build errors if ScriptHost.tlb was not present. [SRSTUDIO-2740]

Objective Grid
Fixed incorrect location of CellTips on multi-monitor displays. [SRSTUDIO-1304]
Fixed build errors caused by incorrect use of GetTickCount64(). [SRSTUDIO-5719]
Fixed unexpected re-enabling of Undo in HideCols(). [SRSTUDIO-6232]

ROGUEWAVE.COM 7
 Known Bugs

Objective Toolkit
Focus issue in floating MDI child windows
Under certain conditions, apparently related to Windows Update KB3153199, when you float an MDI
child window the applications mainframe (derived from SECMDIFrameWnd) may not respond to some
mouse clicks in the non-client area. Activating a non-floating MDI child window will restore normal
operation. To work around this problem, override SECMDIFrameWnd::OnActivate(), copying the code
from this method in /Src/Toolkit/mdi/swinmdi.cpp. Near the end of this method (around line 2470 in
the original file), replace this line:
NotifyActiveView(nState, pWndOther, bMinimized);

With this:
CFrameWnd* pActiveFrame = GetActiveFrame();
if (!(pActiveFrame->IsKindOf(RUNTIME_CLASS(SECDockableFrame)) &&
((SECDockableFrame*)pActiveFrame)->IsFloating())) {
NotifyActiveView(nState, pWndOther, bMinimized);
}

Then add this entry to your message map:

ON_WM_ACTIVATE()

ROGUEWAVE.COM 8
 Limitations

Installation
General Installation Issues

NOTE >> Each Stingray Studio release is a replacement for, not an upgrade to, the previous version.
Always perform an installation into a new area, and not into the same install directory as a
previous version.

Documentation location changed

User Guides are no longer installed into the Docs folder, but instead are provided online.
These guides are accessible from the Documentation shortcut installed in the Start menu or
from the Stingray Assistant tool.

ROGUEWAVE.COM 9
Rogue Wave provides software development tools for mission-critical applications. Our trusted solutions
address the growing complexity of building great software and accelerates the value gained from code across
the enterprise. Rogue Waves portfolio of complementary, cross-platform tools helps developers quickly build
applications for strategic software initiatives. With Rogue Wave, customers improve software quality and
ensure code integrity, while shortening development cycle times. Rogue Wave Software, Inc. All Rights
Reserved

ROGUEWAVE.COM 1
0