[Ray Konopka]

Hi Dave. Thank you for bringing this to our attention. Yes, the parser needs to be updated to handle inline variable and constant declarations introduced in Rio.

Ray

[Ray Konopka]

The Palette Menu for 10.3 is now available for download.

As for multi-column, I’m not sure what you are referring to. You can use the Palette Menu to group pages into separate categories which show up as cascading menus, but it is not really column based.

Ray

[Ray Konopka]

Hi,
The issue is that the new installer that Embarcadero created for the KSVC for 10.3 Rio did not add the necessary directories to the C++ related paths. I have already reported this issue to Embarcadero. In the meantime, you can resolve the issue manually by following the steps below.

In order to fix the issue, we need to add the appropriate KSVC directories to the System Include and Library paths for the C++ compilers. To make the instructions easier to read, consider the following two variables, which define the two paths that are needed.

KSVC_PATH_WIN32=$(BDSCatalogRepositoryAllUsers)\KonopkaControls-260-6.2.3\Lib\RX10.3\Win32

KSVC_PATH_WIN64=$(BDSCatalogRepositoryAllUsers)\KonopkaControls-260-6.2.3\Lib\RX10.3\Win64

Please perform the following steps:

1. Close all files in RAD Studio 10.3
2. Open the Tools > Options dialog
3. User the tree on the left and navigate to Language > C++ Options > Paths and Directories
4. Select “Windows 32-bit” in the Selected Platform combo box
   a. Make the “Compiler” tab active
      i.  Edit the System Include Path value and add the KSVC_PATH_WIN32 value to the path
      ii. Edit the Library Path value and add the KSVC_PATH_WIN32 value to the path
   b. Make the “Classic Compiler” tab active
      i.  Edit the System Include Path value and add the KSVC_PATH_WIN32 value to the path
      ii. Edit the Library Path value and add the KSVC_PATH_WIN32 value to the path
5. Select “Windows 64-bit” in the Selected Platform combo box
   a. Make the “Compiler” tab active
      i.  Edit the System Include Path value and add the KSVC_PATH_WIN64 value to the path
      ii. Edit the Library Path value and add the KSVC_PATH_WIN64 value to the path
   b. Make the “Classic Compiler” tab active
      i.  Edit the System Include Path value and add the KSVC_PATH_WIN64 value to the path
      ii. Edit the Library Path value and add the KSVC_PATH_WIN64 value to the path
6. Click the Save button to close the Tools > Options dialog box and save the changes
7. Reopen your project. You should be able to build and run your project now.

Ray

• This reply was modified 7 years, 3 months ago by Ray Konopka.

[Ray Konopka]

Hi Navid,

I am able to see KSVC in the GetIt Package Manager for 10.3 Rio. I searched for “KSVC” and the Bonus KSVC 6.2.3 item appeared in the list.

Ray

[Ray Konopka]

Hi Rich,

Yes, CodeSite does support dynamically changing the log file. I suspect that you are changing the original TCodeSiteDestination object when you change the FilePath and not the CodeSiteManager’s DefaultDestination property (or an individual logger’s Destination property).

The CodeSiteManager.DefaultDestination property is not a component reference property. It is more like the Items property of a ListBox. You can assign a TStringList to ListBox1.Items to populate the list box. But if you change the contents of the string list, the list box does not get updated. Here is some sample code that should help illustrate the situation:

uses
  CodeSiteLogging;

procedure TForm1.FormCreate(Sender: TObject);
var
  Dest: TCodeSiteDestination;
begin
  Dest := TCodeSiteDestination.Create( Self );
  Dest.LogFile.Active := True;
  Dest.LogFile.FilePath := 'C:\Temp';
  Dest.LogFile.FileName := 'Sample.csl';

  CodeSiteManager.DefaultDestination := Dest;
end;

procedure TForm1.btnSampleMessageClick(Sender: TObject);
begin
  CodeSite.Send( 'Sample Message' );
end;

procedure TForm1.btnChangeLogFileClick(Sender: TObject);
begin
  CodeSiteManager.DefaultDestination.LogFile.FileName := 'NewLogFile.csl';
end;

The form simply has two TButtons dropped on to it. At the start the DefaultDestination is set to log all messages to the Sample.csl file. Clicking the btnSampleMessage button simply sends a simple CodeSite message. The messages will be logged to the Sample.csl file.

When the btnChangeLogFile button is clicked, the LogFile.FileName property of the CodeSiteManager.DefaultDestination is changed. Now, when the btnSampleMessage button is pressed, the CodeSite message will be sent to the NewLogFile.csl file.

As an alternative, you could create a new CodeSiteDestination object with the updated FilePath and then assign that to the DefaultDestination property.

Ray

[Ray Konopka]

Hi Roger,

Please send an email to sales@raize.com and we will send you the updated link.

Ray

[Ray Konopka]

Hi,

The TRzButton does not provide that level of customization. By default the appearance of the button is driven by the current Visual Style that is active. If you set the ThemeAware property to False, you can get a little more control of the appearance of the button. However, to modify the appearance of the button while disabled, you would need to create a custom descendant of the button.

Ray

[Ray Konopka]

Hi Paul,

I’m not sure which 8 components you are referring to. The KSVC controls only support VCL. Well, I suppose the nonvisual controls in KSVC could also be used in an FMX application.

I’m not sure what plans Embarcadero has for the Signature controls. I do know that there is a big push for High DPI support. I do not know if there are plans for migrating some of the functionality in KSVC to FMX controls.

Ray

[Ray Konopka]

It turns out that Embarcadero did not change the version number of the components–Ugh. So the version number is still 6.2.3, but the version that is available in the 10.3 Rio GetIt Package Manager is built for Rio.

Ray

[Ray Konopka]

I apologize for the delay in responding. Been rather busy getting new versions of our Raize Software products released.

Back to your question. From the code you provided, it looks like you are using VCL Styles. Is that correct? Then in that case, the technique I provided above will not work. The reason is because the button is designed to pickup the custom style when active. The default behavior of the TRzToolButton is to pickup the background and font colors from the style. I’m not quite sure what appearance you are trying to achieve since you are essentially getting rid of the gradient and hiding the button frame. What style are you using? and what appearance are you trying to achieve?

Ray

[Ray Konopka]

That is an excellent question. I am trying to get the answer to that as well.

Ray

[Ray Konopka]

You’re welcome. I’m glad you saw the notice on the website.

Ray

[Ray Konopka]

Hi,

There is no built-in properties to allow this, but you could write event handlers for the OnMouseEnter and OnMouseLeave events and do something like this:

procedure TForm4.RzToolButton1MouseEnter(Sender: TObject);
begin
  RzToolButton1.Font.Color := clRed;
end;

procedure TForm4.RzToolButton1MouseLeave(Sender: TObject);
begin
  RzToolButton1.Font.Color := clGreen;
end;

Ray

[Ray Konopka]

Does the C++ Package include the CodeSiteExpressPkg package in the requires clause?

Ray

[Ray Konopka]

Thanks. I’ll fix it. Copy and paste error 🙂

[Author]

Posts