[Ray Konopka]

Hi Barry,

I see the same behavior. I think the issue is in the built-in Variant property editor. In looking at the code for the QuickCompare functionality, there does not appear to be any assumptions that the FieldValue has to be a number.

Have you tried setting the FieldValue at runtime in the FormCreate event handler. I wonder if that would work properly for you.

Ray

[Ray Konopka]

Hi Ulrich,
In short, the custom TRzNotifyIconData structure is probably not necessary. It was originally added because Delphi did not include any support for that data structure at the time. Now that Delphi includes the definition for TNotifyIconData, the Raize version should probably be deleted. It should be possible to do that in the RzTray.pas file and then run the !Build_RC7.cmd (or !Build_RC6.cmd) file in the Source directory to rebuild the DCUs and Packages.

I would also suggest that you create a report in Quality Portal so that Embarcadero can make this a permanent fix.

Ray

[Ray Konopka]

Hi David,
Your best option would be to handle the OnSendMsg event of the CodeSite Loggers that you are using. The event handler is passed three parameters. The Sender represents the CodeSite object that is being used to send the message. The MsgData parameter is of type TCodeSiteMsgData, and represents an object that describes all attributes of the formatted message. The Handled parameter controls whether or not the message is sent to the current destination. Set Handled to True to prevent the message from being sent to the current destination.

Ray

[Ray Konopka]

Hi Steve,

Oh wow. I haven’t really had to think about charsets in quite some time–at least not since Delphi shifted to Unicode support in Delphi 2009. As you noted, the root cause of the issue is in the TRichEdit base control (and perhaps in the underlying Windows Rich Edit control). As such, I would suggest posting a question about this in the Delphi Developer Facebook Group. Perhaps someone there will have some better insight into this.

Ray

[Ray Konopka]

Hi Bob,

The functionality described above is indeed a central focal point of CodeSite 6. A release date for CS6 has not been announced, but I am hopeful for a fall release.

Ray

[Ray Konopka]

Hi Steve,

I would look into encoding the record contents into something like JSON or XML and then put that into the DMTextSource. Then whatever receives the drop can then parse the payload and the reconstitute the record, or put it into some other construct (if dropping on an app that does not know about your record structure).

Ray

[Ray Konopka]

Thanks Steve.
I certainly cannot disagree. It’s one of the main reasons why I have kept this forum going. As I have noted on previous occasions, this whole situation is not what was originally planned. I will continue to engage Embarcadero regarding the components.

Ray

[Ray Konopka]

Hi Luciano,
I am hoping you located the download link for the Palette Menu expert on the Palette Menu page of our website: https://raize.com/palette-menu/

Ray

[Ray Konopka]

Hi Nathan,

I apologize for the delay. For some reason I stopped getting notifications for new posts in the forums. I have the CodeSite Dispatcher running pretty much all the time and I am not experiencing the issue you describe, so it is important to try to figure out what is causing the issue.

From your original post, it sounds like the Dispatcher is reporting the Out of Memory error and not the Live Viewer. Is that correct? Also, is there anything that you can note that results in the Out of Memory to get reported. For example, you noted that you disable the dispatcher and then after a couple days you the error. Does the error just pop up? Or, do you do something first, such as Enable the Dispatcher?

It would also be good to have you send me the CSDispatcherLog.txt file. The file is located at: C:\Users\\AppData\Local\Raize\CodeSite\5.0. Please send me a copy of the log file. Also, the next time the Out of Memory error occurs, grab the CSDispatcherLog.txt file and send that one as well. Please send them to support@raize.com.

Additionally, are you only using the Live Viewer destination? Or, are you sending messages to any other destinations?

And finally, for now, what types of messages are you sending? Basic datatypes like strings, integers, etc. Or, are you sending lots of objects, images, etc.

Ray

[Ray Konopka]

Hi David,

You are correct, not much was done with KSVC in 11.3, and I keep getting more reports of changes that were made (or should I say started) that were not completed and more significantly break other functionality.

As you noted in your original post in this topic, everyone should please continue to keep voting and submitting Quality Portal reports for all issues found. Prefix all reports with “KSVC:” (as requested by Marco Cantu). And yes, I completely agree that it is ridiculous to have to vote to get bugs fixed.

Ray

[Ray Konopka]

So, the TRzSizePanel is technically working as designed. The TRzCustomSizePanel.GetParentWorkingRect method looks at the various controls (and child controls) on the form to determine the range of the sizing bar. In your particular example, the right edge of the Close button is restricting the range of the right SizePanel.

If you were building an SDI application, then I would suggest dropping a Panel into the main client area, setting the Align property to alClient, and then dropping your panel with the Close button onto the client panel and set the Align property to alTop. Then the size panel would function as you expect. However, that approach does not work with an MDI application.

As an alternative, you could align your close panel to be alTop, which would allow the size panel to work properly, but then you do not get the visual layout you are looking for.

Another option would be to modify the TRzCustomSizePanel.GetParentWorkingRect method and comment out the alCustom case label in the middle of the method. This would eliminate the range check for the alCustom panel and then the size panel would be able to be dragged over the sub-panel.

Ray

[Ray Konopka]

Unfortunately, the animated GIF is not animating, so I’m not sure what behavior you are seeing. As for debugging the components, you can add the source directory for the components to your Project Search Path. Then when you rebuild your project, the KSVC source will get recompiled as well and then you’ll be able to step through the code.

Ray

[Ray Konopka]

Hi,

Your best bet would be to change the BlinkIntervalOn value in code (in the FormCreate event handler for the desired form) to prevent the DFM files of the other forms using TRzLabel or TRzStatusPane from getting updated.

Ray

[Ray Konopka]

Hi Nathan,

You are disabling the Dispatcher correctly. When the dispatcher is disabled, CodeSite messages generated from your applications are still sent to the Dispatcher, but the Dispatcher will not forward them onto their destination. The other way to “disable” logging is to set the Enabled property of the CodeSiteManager (or individual CodeSite logger objects) to False in your application.

As for the Out of Memory errors that you are receiving, what version of the CodeSite Dispatcher are you using? Are you running the latest version?

Ray

[Ray Konopka]

Hi Bob,

Originally, the SendCollection did exist, but was eventually replaced with an overloaded Send method that accepts a TCollection parameter. Clearly you found a gap in the documentation. I’ll be sure to fix that for the next release. I apologize for the confusion.

Ray

[Author]

Posts