[Ray Konopka]

Hi Gordon,

While what I stated earlier is indeed true, we discovered that there was an issue with the CodeSite Logging Classes when ASLR (Address Space Layout Randomization) was enabled. The problem affects 64-bit applications and prevents CodeSite messages from being delivered to the CodeSite Dispatcher. As such, Live Logging and File Logging do not work.

We have just released a new 5.4.1 version that fixes this problem. Please see this link for more details: CodeSite ASLR Support

We have also provided Embarcadero with an update to the CodeSite Express edition that is deployed through the GetIt Package Manager. The new 5.4.1 build should be available in GetIt soon.

Ray

[Ray Konopka]

Delphi 11.2 is dcu compatible with 11.0 and 11.1. As such, the latest version of CodeSite will work with 11.2.

Ray

[Ray Konopka]

Hi Steve,
I apologize for the delay. I just created a test app using Delphi 10.2.3 and DropMaster 2.5.2 and the TDMTextTarget component is working just fine in the app.
Are you able to recreate the issue in a test project and send me the source code (no executables) and I can take a closer look?

Did anything change recently with your system? Before Jim went on vacation, he saw your message and thought that it sounded like it might be related to permissions.

Ray

[Ray Konopka]

Hi Steve,
I apologize for the delay. I just created a test app using Delphi 10.2.3 and DropMaster 2.5.2 and the TDMTextTarget component is working just fine in the app.
Are you able to recreate the issue in a test project and send me the source code (no executables) and I can take a closer look?

Did anything change recently with your system? Before Jim went on vacation, he saw your message and thought that it sounded like it might be related to permissions.

Ray

[Ray Konopka]

Hi Dave,

I believe you are getting “Not enough actual parameters errors”.

Yes, Embarcadero needs to update the demo code that comes with the components. In the meantime, you can fix the missing parameter errors with the demo by adding Self as the first parameter to the method calls.

For example,

if UsingSystemStyle then
becomes
if UsingSystemStyle( Self ) then

C := GetGradientPanelFrameColor( FCurrentGCS )
becomes
C := GetGradientPanelFrameColor( Self, FCurrentGCS )

Ray

[Ray Konopka]

Hi Mike,

The event that I mentioned in my response was the OnDblClickOpen event and not the OnDlbClick event. The OnDblClickOpen event handler has the Handled parameter.

Ray

[Ray Konopka]

Hi,

Not in the current version. However, in CodeSite 6, an internal dispatcher will be available, which will mean that the CodeSite Dispatcher application does not need to be installed. The CodeSite Dispatcher will still be available to handle situations where you want to capture CodeSite messages from multiple applications into a single log file.

Ray

[Ray Konopka]

Hi Jan,

Thank you for your interest in the remote logging capabilities of CodeSite. Remote logging leverages the CodeSite Dispatcher to transport CodeSite messages to another CodeSite Dispatcher running on a remote computer. And since CodeSite allows you to specify multiple destinations for your CodeSite messages, you could have an application’s CodeSite messages saved locally in a CodeSite log file as well as being transported to a remote dispatcher where the message could be saved in a “remote” log file, or displayed in the Live Viewer running on the remote machine.
When it comes to logging in general and especially with remote logging, it is important to consider how the logging information is going to be used. You asked about 250 client computers logging to one server. You could certainly configure 250 client computers to transport their CodeSite messages to a single remote computer. Of course, performance is certainly going to be an issue if each client application is sending a high volume of large CodeSite messages.
But even if you will not be taxing the system with lots of data, it is still important to consider what you want to do with the logging information once it is captured. For example, does it make sense for all CodeSite messages from each client to be placed into a single CodeSite Log File on a remote computer? If there are interactions between the various client computers, then perhaps it makes sense to see all the messages in one log file. On the other hand, if the intent is to simply have a remote version of the log so a support staff member can more easily access client logging information, then it may make more sense to have each remote log file include the name of the client computer.
In regards to what kind of server, that will really depend on the volume of CodeSite messages you expect to be sending, and what payload those messages will contain. For example, sending a simple CodeSite message that logs the current value of a property is much different than a CodeSite message that captures all of the published properties of the current form, which is much different than a CodeSite message that contains a screenshot of the current desktop.

Ray

[Ray Konopka]

Hi Mike,

You can create an event handler for the OnDblClickOpen event of the TRzShellList and in the handler set the Handled parameter to True. For example:

procedure TForm38.RzShellList1DblClickOpen(Sender: TObject; var Handled: Boolean);
begin
  Handled := True;
end;

Ray

[Ray Konopka]

Hi Andreas,
I’m not sure what happened but some of your messages were marked as spam. I do not know why they were marked as spam. Regardless, I have removed the spam marker and your posts should now appear for everyone.

Ray

[Ray Konopka]

The Delphi compiler version for Delphi 10 is 30, which matches the “Found version: 30.0” in the error message. But the error message also says that version 32.0 was expected. This means that the Delphi 10.2 compiler was being used to compile the code.

Please look in the !Build_RC6.cmd file and check to make sure that the VCLVersion, DCC32EXE, and DCC64EXE variables are set correctly.

Ray

[Ray Konopka]

Never mind. I see your other post with the details.

Ray

[Ray Konopka]

Hi Johnson,

What does the output look like when you try building the components with the !Build_RC6.cmd file?

Ray

[Ray Konopka]

Hi Barry,

In order to save the specified property values to the property store (i.e. registry) you need to call the Save method (RzPropertyStore1.Save). For example, when your app closes.

Likewise, at startup (e.g. FormCreate) you need to call the Load method to instruct the TRzPropertyStore component to load the stored property values and apply them to the components.

Ray

[Ray Konopka]

Hi Patrick,

Thanks for taking the time to share your investigation of this issue and for posting the solution. I would encourage you to create a new issue on Embarcadero’s Quality Portal to report this issue and your findings.

Since Embarcadero acquired the components in 2015, an official fix will need to come from them. Therefore, I am encouraging all KSVC users to report issues and enhancement requests to Embarcadero directly. I will continue to engage Embarcadero to encourage them to address issues like this and keep the library current, but I believe it will be good for Embarcadero to see issues being reported by other users.

Thanks again for sharing your findings!

Ray

[Author]

Posts