[Ray Konopka]

Hi Rhett,

Thank you for the clarification. I’m sorry I misunderstood your post. I thought it was in response to the previous post. As for the style issues with 10.4, I really wish I could share some positive news. I’ve certainly been trying from my side, but the ball is in Embarcadero’s court as they say.

Ray

[Ray Konopka]

Hi Navid,

I apologize for the delay in responding. I missed the notification. As for the uninstaller, I will certainly look into the installer script to make it is operating correctly. As for manually uninstalling CodeSite, you can execute the following command in the directory where CodeSite is installed:

UNWISE.EXE CS5_Install.log

Ray

[Ray Konopka]

Hi Rhett,

Unfortunately, I have not experienced this particular error with GetIt, nor have I heard of any reports. Have you contacted Embarcadero about this?

Ray

[Ray Konopka]

Hi John,

Sorry for not responding sooner. Yes, the changes necessary in !Build_RC6.cmd are pretty straight-forward. Glad to hear you were able to move forward.

Of course, it would be even better if you didn’t have to make any modifications at all and Embarcadero would create the deployment correctly.

Ray

[Ray Konopka]

Hi Barry,

The Cells property is a convenience property for accessing portions (i.e. cells) of an item already in the list. The property makes it easier to extract a specific piece of information as well as updating a specific piece instead of having to work with the entire item.

For example, in the following example, a new item is added to the list and then the Cells property is used to change the ‘b’ to ‘Hello’.

RzTabbedListBox1.Add( ‘a’#9’b’ );
RzTabbedListBox1.Cells[ 1, 0 ] := ‘Hello’;

Ray

[Ray Konopka]

Hi Lucian,

Another customer ran into a similar issue. We provided the steps that Embarcadero recommends for “resetting” a GetIt Package, but apparently, they did not work. We’ll have to do more research into that. In the meantime, I’ve made the CodeSite Express installer for 10.3 available on our website.

https://raize.com/wp-content/uploads/CS5_Express_RX103.zip

Download and unzip the file, then run the installer. Make sure the IDE is closed before running the installer.

Ray

[Ray Konopka]

Hi Larry,

For version 6, all the CodeSite Tools will be 64-bit. However, we do not have a release date for CS6 yet.

From the report it looks like you are using version 5.2.1 while the latest release of the CodeSite Tools is 5.3.4. Have you tried updating the tools to the latest version? We recommend doing so because there have been issues fixed in the Dispatcher.

Why do you believe that the Out of Memory issue is connected with the tools being 32-bit apps? We have many customers (ourselves included) that utilize CodeSite logging in large applications running on Win64 systems. We would be interested in learning how you are using the software. That is, are you logging to the Live Viewer or a CodeSite Log File? What type of application are you building? What types of CodeSite messages are you logging? And approximately how many messages are you logging?

Ray

[Ray Konopka]

Hi Hans,
I’ll add that request to the enhancement list.

Ray

[Ray Konopka]

Hi,

Unfortunately, at the moment, I do not have a solution to the issues that you (and others) are running into with 10.4. However, I do know that the display issues are occurring because the IDE is now using a custom VCL Style and not the system style, while the form designer is applying a different style.

The problem is that the controls in the library have not been modified to account for this IDE change. (Actually, Embarcadero has made no modifications to the controls since they acquired them, but that’s another story.)

Anyway, the controls are designed to adjust their appearance using the active style. At design-time (in 10.3 and earlier), the active style has always been the Windows style, but in 10.4, the active style applied to the RAD Studio application is either the Light or Dark VCL Style. As such, the KSVC controls pickup their settings from those styles at design-time.

The controls are designed such that if the Windows style is used and custom colors are chosen, then the custom colors are used. However, in the 10.4 design-time environment, the Windows style is not used, and thus the custom colors are not shown. However, if you run the application, then the controls will appear correctly at runtime. I realize that it is very disconcerting to have the design-time appearance not match what is expected.

I wish I could respond with more positive news. I’ll just close that I am extremely frustrated with the way Embarcadero has handled the components. I am investigating ways to address these issues.

Ray

[Ray Konopka]

Hi Lars,
The frames of buttons and edits are handled by the current style of the operating system, or if you are using VCL Styles. There are some additional levels of customization when it comes to Custom Framing for edit controls, but rounded corners are not one of the features required.

Ray

[Ray Konopka]

I think I found out what is happening. I suspect that your application is using the TRzBalloonHints component. Is that correct? When I dropped a TRzBalloonHints component onto my form, I get a similar display issue that you are seeing. The hint caption gets wrapped too soon regardless of how wide the CaptionWidth is set to. Fixing this will require modification to the TRzBalloonHints (or not using the TRzBalloonHints component). I suspect that this issue has been in the components for quite a long time. It’s just that no one ran into it before.

Ray

[Ray Konopka]

Hi Barry,

What version of Delphi are you using? And what version of Windows? And what version of the components?

I created a test app using Delphi 10.4 running on Windows 10 and I got the following:

Ray

[Ray Konopka]

I wonder if it related to some other property setting that you have changed on the form. Such as Position. Would it be possible to have you send me the DFM file for your main form? If so, send it to our support email address and I’ll take a look.

Ray

[Ray Konopka]

Hi Barry,

The nbFirst is conflicting with the enum for the TDBNavigator. Easiest way to resolve is to prefix the enum with the enum type. For example,

dbNav.BtnClick( TRzNavigatorButton.nbFirst );

You could also rearrange the units in the uses clause, but I tend to like adding scope to avoid the conflict regardless of the order of unit names.

Ray

[Ray Konopka]

Well, since they currently own the components, I guess you could. However, I have no confidence that they will do anything about it. I’m trying to figure out what to do.

Ray

[Author]

Posts