[Ray Konopka]

The TRzListView implements a slightly different hinting support originally added to provide better support for the TRzBalloonHints component. The issue was that hinting in the base TListView did not handle custom regions (as used by balloon hints).
Unfortunately, there is no property that controls that behavior. To prevent the OnInfoTip event from firing, you would have to modify the source code for the TRzListView.
Is the frequent calling of the OnInfoTip event causing an issue? What are you doing in the OnInfoTip event handler?

Ray

[Ray Konopka]

Hi,
The CS5_Tools.zip file from the Raize Software website is the installer for the CodeSite Tools, which includes the CodeSite Dispatcher, CodeSite Controller, CodeSite Live Viewer, and CodeSite File Viewer. The CodeSite Tools does not contain and of the logging classes, which are used by application code to capture and log information.
I recommend reviewing the https://raize.com/codesite/ page for a more complete description of the various pieces of CodeSite.
The bottom line is that the CodeSite Tools is not a test version of CodeSite, and we do not offer a Trial Edition of CodeSite. We do offer a 30-day money back guarantee if you are not satisfied with the product.

Ray

[Ray Konopka]

Hi,

The OnDrawItem event in TRzListView is inherited from the TListView control. That is, the event is generated by the inherited behavior of the TListView (and more precisely, the TCustomListView) class. According to the Help for TListView, the OnDrawItem event only fires when CustomDraw is also set to true. You may wish to take a look at the other drawing related events such as OnAdvancedCustomDraw, OnAdvancedCustomDrawItem, etc.

Ray

[Ray Konopka]

Hi,
I suspect that you installed CodeSite Express. Is that correct?

CodeSite Express does not include the Raize.CodeSiteLogging.dll .net assembly. DotNet support is only available in CodeSite Studio.

Ray

[Ray Konopka]

Hi Steve,

Yes, the current version of CodeSite will work with 10.4.2.

Ray

[Ray Konopka]

Ah, I see. Interesting. The drop down is causing a focus change and that is repopulating the content area. Unfortunately, the code would need to be modified in order to change this behavior, and even then I’m not sure it would be possible to change this behavior. The same thing happens with the standard TComboBox–it may be intrinsic to the combo box Windows control. Hopefully, turning off AutoDropDown will be sufficient.

Ray

[Ray Konopka]

Interesting request. I understand what you are requesting, but I’ll need to think about this a bit more. It really only makes sense for a single application. Gets much more complicated when multiple applications are logging to the Dispatcher. There are significant changes coming in CodeSite 6, and it may be possible to provide some information in certain configurations.

Ray

[Ray Konopka]

Hi Steve,

I tried to duplicate what you described by doing the following:
1. Create new VCL Application (btw, I’m using Delphi 10.4)
2. Drop a TRzComboBox and a TRzEdit onto the form.
3. Edit the Items of RzComboBox1 and add the three “John” names plus a couple others.
4. I then ran the application.
5. I typed “John” without the quotes into the combo box and “John Anderson” get displayed with the ” Anderson” highlighted.
6. I then pressed the Delete key to delete the selected text.
7. I then pressed the Tab key to switch to the RzEdit1.
8. The combo box still showed just “John”.

Do you have any other event handlers on the combo box that could be causing the behavior you are seeing?

Ray

[Ray Konopka]

Hi David,

The High DPI issues will be addressed in the next release.

Ray

[Ray Konopka]

Hi,

Thanks for the additional information. In short, you would like an easier way to log the parameters to a method call. A plug-in will not really help you capture the information you want. Instead, you need an overloaded EnterMethod method to allow your LogParams technique to work, or some other technique. I’ll have to give this some more thought.
What does the output look like in the Viewer after calling CodeSite.Send using your LogParams object?

[Ray Konopka]

The update addresses the critical issues that affected the components from working/displaying properly in Sydney. Specifically, the changes to VCL Styles and StyleServices. In addition, where applicable, the components support the StyleElements property. The new StyleName property added in 10.4 is also supported. There were some other issues addressed as well (e.g. issues in TRzCheckList, display issues in TRzDBGRid, TRzStringGrid, TRzProgressBar, TRzPageControl, TRzTabControl, etc.)

Ray

[Ray Konopka]

Hi Martijn,

Unfortunately, it was not a “simple” fix, and as a result, really needed to be address in a new release. Fortunately, that is finally coming.

Ray

[Ray Konopka]

Hi,

Yes, it is technically possible to write a custom plug-in for the CodeSite Viewers. The Compare Objects and Compare MemStatus plug-ins are built as separate packages that are loaded into the Viewers on startup.

What type of plug-in are you looking to create?

Ray

[Ray Konopka]

Hi Navid

ScratchPad does not include a manifest to tell Windows that it supports High DPI. As a result, when you run ScratchPad on a high resolution monitor, Windows automatically scales the display up to fit. Therefore, you are certainly able to use the application. All the menus, toolbar buttons, dialogs all appear the correct size. However, since Windows is scaling the bitmap rendering of the app, the menu fonts and toolbar button images are a little pixelated.

Ray

[Ray Konopka]

Hi Steve,

For a TRzTabSheet in a TRzPageControl, there is a TabIndex and a PageIndex. If all the tabs are visible, then the two values will be the same. However, if any of the tab sheets have their TabVisible property set to False, the TabIndex and PageIndex for a specific TRzTabSheet may indeed be different. The PageIndex always represents the “index” of the particular tab sheet in relation to the other pages in the page control. The TabIndex represents the index of the physical tab displayed that is associated with that tab sheet.

You are getting odd results because you are indexing into the Pages collection using a TabIndex instead of a PageIndex. But the OnPaintTabBackground event does not provide a PageIndex, just a TabIndex. Fortunately, there is a PageForTab method available to handle that. If you change your method to the following, you will get the behavior you are expecting:

procedure TForm14.RzPageControl1PaintTabBackground(Sender: TObject; ACanvas: TCanvas; ATabIndex: Integer;
  const ARect: TRect; var Handled: Boolean);
begin
  with (Sender As TRzPageControl).PageForTab( ATabIndex ) do
  begin
    if (tag = 0) then // if tab is set to tag = 0
      ACanvas.Brush.Color := clYELLOW // color yellow
    else // else
      ACanvas.Brush.Color := clWhite; // color white
  end;

  ACanvas.FillRect(ARect); // paint the tab
  Handled := True; // show its handled
end;

Ray

[Author]

Posts