[Ray Konopka]

Hi,

Is there anyway that you can get access to the machine? Or at least have a user access the Dispatcher Log on that machine?

If the disk was getting so full that the Dispatcher was unable to update the log file, then the Dispatcher should record the error in the Dispatcher Log and then continue to process the next message. The next message would then have a problem as well, log the problem, and continue. Clearly the Out of Memory error suggests that something is not getting cleaned up correctly in this situation.

In addition to check the Dispatcher Log, I would suggest terminating the CSDispatcher.exe and then check the hard disk. Is the disk really full? Or, was the CSDispatcher just eating memory.

Finally, do you know what version of the CodeSite Dispatcher is running on that machine?

Ray

[Ray Konopka]

Hi Ian,

I suspect that the root cause of the problem may lie in how you have 10.3 configured. I have 10.3.3 installed and am using the KSVC (installed via GetIt) without any of the problems that you are reported. Also, the fact that you have also been having issues with other libraries makes me believe there might be something wrong in the IDE config.

When you posted “If I drop them on the form…”, as this form part of an existing project? Or a brand new VCL project?

The F2063 compiler error usually means that you have a directory on your Library Search path that already has *.dcu files for the referenced units, but they were built with an old version of Delphi. So, I would check all the directories on your Library Search Path and see if there are some Rz*.dcu files located on any of them. I would also check the directories of the project you are trying to compile. If you find any Rz*.dcu, I suspect that these were added by the compiler. Normally, this should not happen, but it would happen if you added the Raize Components Source directory to your project at some point so the component units would get rebuilt by the compiler.

Hope this helps,
Ray

[Ray Konopka]

Unfortunately, supporting StyleElements throughout the library is something that I have wanted Embarcadero to tackle since acquiring the components. Unfortunately, the appearance of the TRzControlButton (i.e. the class that controls the embedded buttons) is handled in the TRzControlButton.DrawBtnFace method and that method does not look at StyleElements nor is there a UseThemes type property available either.

Ray

[Ray Konopka]

Hi,

I created a test project and I am unable to duplicate the issue you are reporting. I dropped a TRzCheckGroup and two buttons on the form. In the first button, I added several items to the check group. In the second button I clear the check group. I then ran the app and loaded the items, checked some items, and clicked the second button to clear the group. No issues.

I am wondering if you have any other interactions going on in your project? Are you able to duplicate the issue in a test project? If so, please send the source (no exes) to support@raize.com and I’ll take a look.

Ray

[Ray Konopka]

Hi Hans,

I’m so glad to hear that the CSSearchFiles tool helped you locate what you were looking for more quickly. And thank you for bringing up your request on this forum. I love to hear how people are using (or would like to use) CodeSite. You never know when it may spark a new feature or supporting tool!

Ray

[Ray Konopka]

Hi,

The new CSSearchFiles command line tool is now available:
https://raize.com/wp-content/uploads/CSSearchFiles.zip

The usage information for CSSearchFiles is shown below. Running CSSearchFile.exe without any command line parameters will also display the usage information.

Remember that the message number displayed next to each match can be used to jump directly to that message while in the CodeSite Live Viewer or CodeSite File Viewer.

Ray

CodeSite Search Files 5.3.3
Copyright (c) 1998-2018 by Raize Software, Inc.  All Rights Reserved.

Usage:
  CSSearchFiles [-type:<MsgTypes>] [-text:<Text>] [-trim:<Columns>] <Files>

  MsgTypes:  Search for specified message types (e.g. EX)
             N=Notes | W=Warnings | E=Errors | X=Exceptions

  Text:      If search text includes spaces, wrap in double quotes
  Columns:   Trim output to column width (e.g. 80)
  Files:     Path to CodeSite file(s) to search (e.g. C:\Logs\*.csl)

Examples:

CSSearchFiles -type:EX *.csl
  Search for all Error and Exception messages in all CodeSite log files
  in the current directory

CSSearchFiles -text:"Print Report" *.csl
    Search for all messages that contain "Print Report" in message text

[Ray Konopka]

Hi,

Unfortunately, Delphi 10 Seattle support was added to the components after Embarcadero acquired the components from us. Also, complicating matters is that with the initial release of Delphi 10 Seattle, Embarcadero began selling the components as a subscription. Eventually, Embarcadero stopped selling the components and made them available to all RAD Studio users–starting with Delphi 10.1 Berlin.

Things got even easier with the release of Delphi 10.2 Tokyo and Delphi 10.3 Rio where the Konopka Signature VCL Controls are available in the GetIt Package Manager.

If you have to use Delphi 10 Seattle, then I’m afraid you will need to contact Embarcadero about getting access to the components.

Ray

[Ray Konopka]

Hi Hans,

At first I was going to suggest the CSMergeFiles tool to combine all your logs into one (or a few) log files, but then I realized that the CSMergeFiles tools works by taking two log files and creating a merged log file. Combining 300+ log files would be nearly as tedious as loading each one into the viewer.

This gave me an idea–a new command line tool called CSSearchFiles where you specify a log filename or a wildcard along with what types of messages you are looking for (e.g. Warnings, Errors, Exceptions, Notes) and the tools rips through each of the log files that match the file mask and writes on the console any matches including the message number. Then load the corresponding log file into the viewer and select Search > Jump to Message and enter the message number from the output.

The tool is working, but I need to do a little bit more to polish it up. I’ll make the tool available in the next day or two. Here’s a screenshot of the current version.

Ray

• This reply was modified 4 years, 8 months ago by Ray Konopka.

[Ray Konopka]

Hi,

I am also running the latest version of Windows 10 and I just created a quick test app where I dropped a button and a TRzLauncher component on the form. I then wrote the following event handler for the button’s OnClick event:

procedure TForm32.RzButton1Click(Sender: TObject);
begin
  RzLauncher1.FileName := 'C:\Users\rkonopka\Pictures\sample.jpg';
  RzLauncher1.Launch;
end;

I then ran the program and clicked the button. The Windows Photo Viewer (my default app for JPG files) was launched correctly. Do you have any other property changes from the defaults in the TRzLauncher?

Ray

[Ray Konopka]

Hi David,

Unfortunately, not really. Technically, they did modify the installation such that the components could be installed via GetIt without running a custom installer. Unfortunately, there were some issues with what they did. As for the components, themselves, no. Unfortunate, indeed.

Ray

[Ray Konopka]

It certainly sounds like the locale ID not being saved is definitely having something to do with the behavior you are seeing. The only thing that I can think of is that one or more files are marked as read only and when you go to change it, they are not changing.

Have you tried running Delphi as an administrator and then try to change the locale?

Ray

[Ray Konopka]

Hi Barry,

A couple things to check/try.

1. Drop a new button on your app and add the following in the event handler. The code essentially performs the same steps that the TRzVersionInfo component provides. As such, I am expecting that you will be getting the Version Info Not Available message when you run it.

procedure TForm24.RzButton1Click(Sender: TObject);
var
  InfoSize, Temp: DWord;
  FilePath: string;
  PathStz: array[ 0..MAX_PATH ] of Char;
begin
  GetModuleFileName( HInstance, PathStz, SizeOf( PathStz ) );
  FilePath := PathStz;

  InfoSize := GetFileVersionInfoSize( PChar( FilePath ), Temp );
  if InfoSize > 0 then
    ShowMessage( 'Version Info Available' )
  else
    ShowMessage( 'Version Info Not Available' );
end;

2. If you were to look in the source for the TRzVersionInfo component, you would see that the above code actually checks the FilePath property first. So, my next question, have you assigned anything to the TRzVersionInfo.FilePath property either at design-time or runtime?

And finally, I’ll look into how we can allow images to be added to forum posts.

Ray

[Ray Konopka]

Hi Martijn,

While the google results may not show it, other users are indeed running into these sort of HighDPI related issues with the components. Embarcadero has done quite a bit of work in the VCL to provide better support for HighDPI, and I keep asking when the same work will be applied to KSVC (Embarcadero acquired KSVC in 2015), but as of yet no work has been done. It is very disappointing. As such, I would strongly suggest that you submit your bug report to Embarcadero.

Ray

[Ray Konopka]

Hi Barry,

Sorry for the delay. I missed your response. Anyway, I created a brand new VCL app in 10.3.3 to try out the version info and everything worked as expected. Specifically, I just created a new VCL Forms app. Dropped a TRzVersionInfo component and a few TRzVersionInfoStatus controls on the form. I hooked them all up and then went into the Project Options (Version Info was already turned on). I then changed the Version fields (which updated the FileVersion property). I also changed the Product Version field to be something different so that I could test both status fields. All the data was displayed correctly.

I then went and changed the Locale ID on the VersionInfo page to be English(United Kingdom) and rebuilt and ran the app, and the version info was displayed correctly.

I’d be curious to know if you repeat the above steps does everything work, or do you get the same issue.

Ray

[Ray Konopka]

Hi,

Thank you for reporting this. There is definitely an issue with the new KSVC GetIt package that Embarcadero created for 10.3. You are correct, the RaizeComponentsVcl.a file is missing from the Lib\RX10.3\Win64 directory.

I would strongly recommend that you report this to Embarcadero so that they can fix it for the next release (or in an update).

In the meantime, you can rebuild the component packages (including the RaizeComponentsVcl.a file) using the !Build_RC6.cmd file located in the Source subdirectory. Unfortunately, the version of the !Build_RC6.cmd file that was included in the latest version of KSVC is not up to date. You can download an updated version from the following link. https://raize.com/wp-content/uploads/Build_RC6.zip

After downloading, unzip the contents and replace the !Build_RC6.cmd file in the C:\Users\Public\Documents\Embarcadero\Studio\20.0\CatalogRepository\KonopkaControls-260-6.2.3\Source directory with this new version. You will need to edit the command file to make sure that the path to the 10.3 compiler is correct for your machine. The command file will only display a message until you edit the file and uncomment a particular line to allow the build process to continue.

Once you follow the instructions for editing the file, open a Command Prompt (we recommend opening it As an Administrator). Then you MUST navigate to the C:\Users\Public\Documents\Embarcadero\Studio\20.0\CatalogRepository\KonopkaControls-260-6.2.3\Source directory, and then you can execute the !Build_RC6.cmd file. This will rebuild the components and packages and when it is complete, you will find the RaizeComponentsVcl.a file located in the Lib\RX10.3\Win64 directory.

Ray

[Author]

Posts