[Ray Konopka]

Hi David,
CodeSite 5 (and earlier) uses the QueryPerformanceCounter to generate a timestamp for each message. The count is compared to a base count value at app start up to generate a time stamp. From what you describe, it sounds like QueryPerformanceCounter is not returning an accurate count after the host machine is returned from hibernating. Just to be clear, you mention that you hibernate the host machine and not the VM itself. I’m curious if other time values are affected when you resume from hibernation. For example, what does the clock in the system tray show immediately after resuming?

BTW, the QueryPerformanceCounter was necessary in order to get a more precise timestamp value (ms resolution). However, this is no longer necessary with modern versions of Windows. As a result, CodeSite 6 no longer uses the QueryPerformanceCount and instead utilizes the TStopWatch class.

Ray

[Ray Konopka]

Hi Jeremy,
Thanks for sharing your findings. The solution that I came up with essentially does the same thing but instead of calling ResetHeaderHandle in the WMNCPaint method, I call it in the SetViewStyle method:

procedure TRzCustomListView.SetViewStyle( AValue: TViewStyle );
begin
  if ( AValue <> ViewStyle ) then
  begin
    inherited;
    if AValue = vsReport then
    begin
      SetHeaderODStyle;
      {$IFDEF RX12_OR_HIGHER}
      ResetHeaderHandle;
      {$ENDIF}
    end;
  end;
end;

This way the header handle is reset only when the view style is changed as opposed to each time WMNCPaint is called.

Ray

[Ray Konopka]

Hi Jeremy,
Thanks for sharing your findings. The solution that I came up with essentially does the same thing but instead of calling ResetHeaderHandle in the WMNCPaint method, I call it in the SetViewStyle method:

procedure TRzCustomListView.SetViewStyle( AValue: TViewStyle );
begin
  if ( AValue <> ViewStyle ) then
  begin
    inherited;
    if AValue = vsReport then
    begin
      SetHeaderODStyle;
      {$IFDEF RX12_OR_HIGHER}
      ResetHeaderHandle;
      {$ENDIF}
    end;
  end;
end;

This way the header handle is reset only when the view style is changed as opposed to each time WMNCPaint is called.

Ray

[Ray Konopka]

Hi Roberto,

I apologize for the delay in responding because of the Christmas holiday. Working backwards from your posts, you are correct in that all you are losing with the design packages not loading is the design-time components, which we only provided for backward compatibility and have not recommended using them for a very long time. In fact, for CodeSite 6, there will be no design packages.

As for why you are having an issue with one of the versions, this is most likely the result of a package change that was introduced with RAD Studio 12.2. Typically, when Embarcadero releases a point update (e.g. *.1 or *.2), the package formats do not change. Of course, none of this applied during the strange times of the 10.x releases where 10.1, 10.2, etc were all major releases. However, when they switched back to regular versioning (e.g. 11, 12), point releases are designed not to have package interface changes. However, they broke that rule with 12.2 with respect to the Modern C++ 64-bit compiler changes.

Bottom line is that you are fine without the design packages. I will also be releasing a new build of CodeSite 5 that will be built with 12.2 in order to support the new Modern C++ 64-bit compiler, so then you should be able to reload the design packages should you wish.

Again I apologize for the delay and the inconvenience all this has caused.

Ray

[Ray Konopka]

Hi Hans,
I apologize for the inconvenience. A new build of CodeSite 5 needs to be released to include support for the 64-bit Modern C++ compiler. I’m trying to fit that into the schedule.
Ray

[Ray Konopka]

Hi David,
Interesting that it logs to the file for a day or two and then stops. Typically, if there is an issue with file logging, it’s immediately apparent, such as file permissions, wrong path, etc. Is it possible that the CodeSite logger is getting disabled at some point in your application? That would cause messages to stop getting logged.

If you have access to the computer, or can get someone to grab a file from the computer, I would like to see the CSDispatcherLog.txt file. It is located in the following path:
C:\Users\\AppData\Local\Raize\CodeSite\5.0\CSDispatcherLog.txt

If you are able to get this file, please send it to support@raize.com and I’ll take a look.

Ray

[Ray Konopka]

The app is called the CodeSite Message Generator. You can download it from the following link:
https://raize.com/wp-content/uploads/CSMsgGenVcl.zip

Ray

[Ray Konopka]

Hi Paola,

The 2.6.0 release specifically adds support for the Modern C++ 64-bit compiler added to RAD Studio 12.2. No other changes were made to the components, so the 2.5.3 version is current. When dragging does not work correctly, that usually means that the format of the drag object has been changed by the vendor. DropMaster includes many demos to provide guidance on how to handle various drag formats from a variety of sources, but the core functionality of the DropMaster components is to provide the framework in which to conduct inter-application drag and drop. I would suggest running the FormatViewer demo program and then drag the information/object that you are interested in onto the FormatViewer window. The demo will then show the various formats that are served but by the other application in the drag operation.

Ray

[Ray Konopka]

Hi Andrew,
I apologize for the delay in releasing DropMaster 2.6.0, but it is now available. Please note that you should also update to RAD Studio 12.2.1 (the newly released inline patch) for proper package compatibility.

If you need the download link for the DropMaster installer, please send an email to support@raize.com

Ray

[Ray Konopka]

Hi Maarten,

It sounds like you are building a Windows Forms App as opposed to a Windows Forms App (.NET Framework). The former uses .NET (formerly .NET Core), while the later uses the .NET Framework. Unfortunately, at this time, the Raize.CodeSiteLogging assembly is built on the .NET Framework.

Ray

[Ray Konopka]

Hi Andrew,
I apologize for the delay in responding. I’ve been waiting for from concrete information from Embarcadero before responding. We have the support for the Modern C++ compiler in 12.2. However, we were informed by Embarcadero that any packages that are created with 12.2 cannot be used with 12.0 or 12.1. We have been told that a hotfix is in the works, and we have been waiting for that hotfix to be released. Once it is, we will be releasing a new DropMaster version.
Again, I apologize for the lack of response.
Ray

[Ray Konopka]

Hi Andrew,
We’ll be releasing a new version of DropMaster 2.x that includes the necessary files to support the modern 64-bit C++ compiler soon.
Ray

[Ray Konopka]

Hi Chris,
Thanks for the report. Unfortunately, I am unable to duplicate the issue, but that could be because I’ve made other changes to the TRzSpinEdit and those affected this particular behavior. However, I would like to confirm that. Are you able to duplicate the issue in a test project? If so, please the source to the test project (no exe) to our support email and I’ll take a look. Also, what version of Delphi are you using?

Ray

[Ray Konopka]

Hi Chris,
It is best to submit them on Embarcadero’s Quality Portal for tracking. When you do, be sure to put KSVC in the subject line for easier identification. Embarcadero does not have a field to specify this library.
Also, I don’t mind if you also post a heads up here to any reports submitted.
Ray

[Ray Konopka]

Hi Nat,

Thank you for providing more information about what you are trying to do–that is, compiling the RCDemo.

Yes, because of some of the changes that Embarcadero introduced into the PROJ file and the fact that RCDemo supports older versions of Delphi, the prompt to select an SDK is presented when you first open the project in Delphi 11. Typically, the built in SDK is automatically selected and the user just clicks the OK button to continue. However, it appears from the screenshot, that you opted to create a new SDK. That is why you were prompted to download other items from Microsoft’s website.

From the remaining issues you describe it sounds like you created an SDK for creating a UWP app and not a standard Win32 (or Win64) app.

I just loaded the RCDemo project (in Delphi 11) on a new VM and I was prompted to select an SDK, but I just selected the default Win32 SDK that was presented. The project loaded, however, when I tried to compile the demo, I did get an error, but it is a known error. Embarcadero did not update a couple of the source files in the demo with the Delphi 11 release. Fortunately, the fixes are straight-forward.

TabsFrame.pas
In: procedure TFmeTabs.Init;
Replace:
if UsingSystemStyle then
With:
if UsingSystemStyle( Self ) then

CustomFramingFrame.pas
In: procedure TFmeCustomFraming.Init;
Replace
if UsingSystemStyle then
With:
if UsingSystemStyle( Self ) then

MainForm.pas
In: procedure TfrmMain.VisualStyleClick(Sender: TObject);
Replace:
C := GetGradientPanelFrameColor( FCurrentGCS )
With:
C := GetGradientPanelFrameColor( Self, FCurrentGCS )

Then you’ll be able to build the RCDemo project successfully.

As for the TRzRegIniFile component, you are correct, that component does not save data for all components. In fact, the TRzRegIniFile is just a conduit to a data store, as I described in a previous post. The TRzFormState component is designed to save certain properties of a form to the data store referenced by the TRzRegIniFile component. To persist the properties of other components in your application, please take a look at the TRzPropertyStore component.

Ray

[Author]

Posts