[Ray Konopka]

Hi Nina,

I believe that all Delphi and C++Builder users are able to download the Konopka Signature VCL Controls (formerly Raize Components) from the GetIt package manager.

Ray

[Ray Konopka]

Hi Gary,

The help should be accessible from within RIO by pressing F1 with a component selected. You can also manually get to the help file and the demo directory by navigating to the installation folder.

For 10.2 (Tokyo) and earlier, the components are installed into C:\Program Files (x86)\Raize\RC6. However, for 10.3 (Rio), Embarcadero created a custom GetIt Installer for the components. They are no longer installed in their usual location. Instead, they are installed in: C:\Users\Public\Documents\Embarcadero\Studio\20.0\CatalogRepository\KonopkaControls-260-6.2.3

Ray

[Ray Konopka]

Hi,

I’m not sure I understand what you are trying to accomplish. The TRzMenuButton does not have concept of selection (hence no ItemIndex property). The intent of the button is to present a popup menu when the user clicks the button. The user then selects the desired menu item from the popup menu.

Ray

[Ray Konopka]

Hi Chris,
I apologize for the delay in responding. Apparently, I had mistakenly marked all posts as read and did not realize I did not respond to your message.

The TRzDBGrid does indeed descend from the TCustomDBGrid component so that it does inherit basic functionality from the ancestor control.

As for adding touch support, I would suggest taking a look at the gesture support included in Delphi. That way you could leverage scrolling without having to interact with the scroll bar itself.

Ray

[Ray Konopka]

The TRzStatusBar uses the standard alignment functionality built into the VCL. In older versions of Delphi, at design-time, there used to be situations where the actual position of the control can change if its left (or top) edge overlaps the left (or top) edge of another control as a result of the bounding size of the parent control changes to become too small.

However, I don’t believe this is still true for more recent versions of Delphi. Is your app doing anything in code to position the controls, set constraints, restore form size, etc?

I’ve tried to duplicate what you are describing, but so far I have not been able to.

Ray

[Ray Konopka]

Transparency in VCL controls that have a window handle (as opposed to TGraphicControl descendants) is handled by the control painting the parent window’s background into the control’s client area. So, the panel is behaving as designed.

I’m not entirely sure what you are expecting a ReadOnly shell list to do, or not to do? From your description you might want to try setting the Enabled property to False, and then change the DisabledColor property to clWindow if you want it to appear active.

Ray

[Ray Konopka]

Hi,

From your description, you have a TRzPanel with Align := alTop and a TRzDBGrid with Align := alClient. Correct?

On the TRzPanel you have placed a series of buttons and combo boxes so that they are positioned vertically centered in the panel. There is no Align property setting to force the controls to be positioned vertically centered in the panel. Therefore, I am assuming that you have simply placed the controls where you would like them. Is this also correct?

I have created a test project with a TRzPanel and TRzDBGrid with their Align properties set as described above and I have not been able to duplicate the effect you are describing. I suspect that you have other settings or configurations that are resulting in the behavior you are seeing.

Are you able to duplicate the overlapping in a new test project with just a TRzPanel and TRzDBGrid? If so, please send the source code (no exes) to support@raize.com and I’ll take a look.

Ray

[Ray Konopka]

Hi Carl,
By disconnecting from the CodeSiteManager, I mean that if you change the CodeSiteManager.DefaultDestination then the logger instance will not use any of those changes.

Setting the CodeSiteManager.DefaultDestination to the new TCodeSiteDestination instance will result in all logger instances using the same destination information.

To log your CodeSite messages to just a log file, you simply create a TCodeSiteDestination instance and only activate the LogFile destination sub-type. An example of this is shown in the Getting Started section of the CodeSite Help.

Ray

[Ray Konopka]

Hi Carl,
Glad you have it working again. I do have a couple comments regarding the code you posted. In your code, you are creating a new Destination object and you are assigning it to both the CodeSite global logger and the CodeSiteManager. By default, each logger instance uses the destination that is defined in the CodeSiteManager. This happens when the logger’s Destination property is nil. By assigning the CodeSite.Destination to a new TCodeSiteDestination instance, you are disconnecting it from the CodeSiteManager.

Ray

[Ray Konopka]

Hi Barry,

The TStringGrid component does not have a SelectedColor property. And since the TRzStringGrid is a direct descendant of the TStringGrid, that property is not inherited to the TRzStringGrid either because it doesn’t exist. Perhaps you were using a different grid control.

Regardless, to customize the coloring of the grid cells, you can use the OnDrawCell event handler. For example, the code below shows a very basic way to change the selection color.

Hope this helps,
Ray

procedure TForm7.FormCreate(Sender: TObject);
begin
  RzStringGrid1.Cells[ 1, 1 ] := 'Delphi 10 Seattle';
  RzStringGrid1.Cells[ 1, 2 ] := 'Delphi 10.1 Berlin';
  RzStringGrid1.Cells[ 1, 3 ] := 'Delphi 10.2 Tokyo';
  RzStringGrid1.Cells[ 1, 4 ] := 'Delphi 10.3 Rio';
end;

procedure TForm7.RzStringGrid1DrawCell(Sender: TObject; ACol, ARow: Integer; Rect: TRect; State: TGridDrawState);
begin
  if gdSelected in State then
  begin
    RzStringGrid1.Canvas.Brush.Color := clGreen;
    RzStringGrid1.Canvas.Font.Color := clWhite;
  end
  else
  begin
    RzStringGrid1.Canvas.Brush.Color := clWindow;
    RzStringGrid1.Canvas.Font.Color := clWindowText;
  end;
  RzStringGrid1.Canvas.FillRect( Rect );
  RzStringGrid1.Canvas.TextRect( Rect, Rect.Left + 2, Rect.Top + 2,
                                 RzStringGrid1.Cells[ ACol, ARow ] );
end;

[Ray Konopka]

Hi,

I’m glad you found it.

For anyone else interested, for 10.2 (Tokyo) and earlier, the components are installed into C:\Program Files (x86)\Raize\RC6. However, for 10.3 (Rio), Embarcadero created a custom GetIt Installer for the components. They are no longer installed in their usual location. Instead, they are installed in: C:\Users\Public\Documents\Embarcadero\Studio\20.0\CatalogRepository\KonopkaControls-260-6.2.3

Ray

[Ray Konopka]

Welcome back! CodeSite’s support for C++Builder is actually provided by the Delphi compiler. That is, the source code is written in Delphi and we first compile it for Delphi and then compile it again using a command line option which causes the compiler to produce the necessary files for use in C++Builder. The .NET logging assembly is written C# and can be used in any .NET managed application. Providing CodeSite support for Visual C++ would require creating a native C++ logging module, which while certainly possible, it is not a trivial matter.

Ray

[Ray Konopka]

Hi Olivier,
There are a few things that I would suggest. First, I would make a report to Embarcadero about this issue as they have been the owners of the components since 2015. Second, the simplest way to handle this for all your clients would be to blank out the Format property, which would use the System defined ShortDateFormat. As for modifying the source code yourself, the approach that I would take would be to do something similar to what is done in the StrToTimeEx function and that is to use the Format property to guide the property. The UseFormatToParse property was added to handle parsing Time values that include other elements not in a format. The same approach could be used to handle date parsing. The only challenge is that the condensing code would need to be tweaked a little to handle the leading ddd in your format string so that it does not get confused for the day elements.

Ray

[Ray Konopka]

I was able to reproduce the problem that you are experiencing. I changed the format settings for Windows to be French (Canada). I only changed the general Format setting. I did not change any of the actually date/time formats.

I then created a test project that has a TRzEdit and a TRzDateTimeEdit control on the main form. I put the TRzEdit so that I could tab into and out of the TRzDateTimeEdit. I also set the Format property of the TRzDateTimeEdit to ‘ddd dd-mmm-yyyy‘. I ran the app, click on the date-time edit and picked today’s date. I then clicked on the other edit control and that is when I got the exception.

After some investigation, I was able to see why the error was occurring. Let me try to explain. As you discovered, the TRzDateTimeEdit uses the StrToDateEx function to parse the information in the edit to determine the date. Because a user is able to enter a date in the control and not select one from the dropdown calendar, the data that gets parsed could be in a variety of formats. In order to interpret the data entered and match it to date elements, the system ShortDateFormat is used as a guide. Well, actually an abbreviated version of the ShortDateFormat is used. For example, the default ShortDateFormat for French(Canada) is yyyy-MM-dd. This gets condensed to YMD. For English(United States), the ShortDateFormat is M/d/yyyy, which gets condensed to MDY. And for English(United Kingdom) the format is dd/MM/yyyy, which gets condensed to DMY.

This approach is how the control is able to handle someone from the US entering 0405 into the control, tabbing away and the date is determined to be April 5. However, someone from the UK entering 0405 into the control will have the date determined to be May 4.

So, what does all of this have to do with what you are experiencing. Well, the condensed ShortDateFormat for French (Canada) as noted above is YMD. However, the Format property of the control is set to ‘ddd dd-mmm-yyyy‘, which gets condensed to DMY. And this is the problem. The parsing code is trying to match the values in the text area to YMD, but the year and day values are swapped. The parsing code ends up matching 2019 to the day value, which is clearly invalid.

The easiest solution is to change the Format property of the TRzDateTimeEdit control to ‘ddd yyyy-mmm-dd‘ so that it matches the YMD ShortDateFormat defined in the system.

Ray

[Ray Konopka]

Hi Olivier,
I will need to do some research on this. What version of Delphi are you using?

Ray

[Author]

Posts