[Ray Konopka]

I apologize for the delay in responding. Been rather busy getting new versions of our Raize Software products released.

Back to your question. From the code you provided, it looks like you are using VCL Styles. Is that correct? Then in that case, the technique I provided above will not work. The reason is because the button is designed to pickup the custom style when active. The default behavior of the TRzToolButton is to pickup the background and font colors from the style. I’m not quite sure what appearance you are trying to achieve since you are essentially getting rid of the gradient and hiding the button frame. What style are you using? and what appearance are you trying to achieve?

Ray

[Ray Konopka]

That is an excellent question. I am trying to get the answer to that as well.

Ray

[Ray Konopka]

You’re welcome. I’m glad you saw the notice on the website.

Ray

[Ray Konopka]

Hi,

There is no built-in properties to allow this, but you could write event handlers for the OnMouseEnter and OnMouseLeave events and do something like this:

procedure TForm4.RzToolButton1MouseEnter(Sender: TObject);
begin
  RzToolButton1.Font.Color := clRed;
end;

procedure TForm4.RzToolButton1MouseLeave(Sender: TObject);
begin
  RzToolButton1.Font.Color := clGreen;
end;

Ray

[Ray Konopka]

Does the C++ Package include the CodeSiteExpressPkg package in the requires clause?

Ray

[Ray Konopka]

Thanks. I’ll fix it. Copy and paste error 🙂

[Ray Konopka]

Hi Steve,
I’ll have Jim, who is the architect of DropMaster, respond to your questions.

Ray

[Ray Konopka]

If the Dispatcher is getting started, then I suspect that you have another CodeSite.Send method being called before you are disabling the logging. To disable logging, be sure to call CodeSiteManager.Enabled := False before sending any CodeSite messages.

Ray

[Ray Konopka]

Thanks for the message. The activation is handled by the forum plug-in that we are using for the site. I’ll look into it.

[Ray Konopka]

Hi Chris,

You may have noticed that the TRzDBDateTimePicker has a grayed icon in the component palette. That is because it is deprecated. And the reason it is deprecated is precisely for the reason that you are running into. Because the TRzDBDateTimePicker (and TRzDateTimePicker) are descendants of the DateTime Picker Windows control, we are limited in what can be done with the content. The handling of null values is just one instance.

Instead, we recommend using the TRzDBDateTimeEdit component. The component does a much better job of handling null fields and allows for freeform input, making it more flexible. Plus, if you are editing field that contains both Date and Time values, you can drop two TRzDBDateTimeEdit controls onto your form and point them both to the same DB Field–one control edits the Date portion and the other edits the Time.

Ray

[Ray Konopka]

Hi Harald,

You can download the CodeSiteJsonLogging unit from the Downloads section of my Delphi By Design blog (https://delphibydesign.com/downloads/). At the bottom of the page, in the CodeSite section, you will find the entry for the CodeSite JSON Logging download.

By the way, the next major release of CodeSite will have integrated support for JSON.

Ray

[Ray Konopka]

Hi,

In order for the OnDrawColumnCell event to fire, you need to set the DefaultDrawing property to False. Then you need to handle drawing the content of all the cells. Here is a simple example:

procedure TForm29.RzDBGrid1DrawColumnCell(Sender: TObject; const Rect: TRect; DataCol: Integer; Column: TColumn;
  State: TGridDrawState);
begin
  if Column.FieldName = 'AB' then
    RzDBGrid1.Canvas.Brush.Color := clRed
  else
    RzDBGrid1.Canvas.Brush.Color := clYellow;
  RzDBGrid1.DefaultDrawColumnCell( Rect, DataCol, Column, State );
end;

The code above results in every cell of the grid having a background of Yellow, except for the ‘AB’ column which has a background color of Red. The DefaultDrawColumnCell method is used to actually to the drawing.

Ray

[Ray Konopka]

I apologize for the delay in responding. I did not realize you asked a follow-up question. Consider the following code. I have dropped a TRzComboBox, a TRzButton, and a TRzLabel onto a form.

procedure TForm29.FormCreate(Sender: TObject);
begin
  RzComboBox1.AddItemValue( 'Item One', '1' );
  RzComboBox1.AddItemValue( 'Item Two', '2' );
  RzComboBox1.AddItemValue( 'Item Three', '3' );
  RzComboBox1.AddItemValue( 'Item Four', '4' );
  RzComboBox1.AddItemValue( 'Item Five', '5' );
end;

The above code adds several items and values to the list. You can get the Values by using the Values list property. For example:

procedure TForm29.RzButton1Click(Sender: TObject);
begin
  RzLabel1.Caption := RzComboBox1.Values[ RzComboBox1.ItemIndex ];
end;

But the problem with this approach is that you need to protect against ItemIndex being -1, which will lead to an Index Out Of Bounds exception. A better approach is to simply use the Value property as shown below:

procedure TForm29.RzButton1Click(Sender: TObject);
begin
  RzLabel1.Caption := RzComboBox1.Value;
end;

Ray

[Ray Konopka]

Hi,
You can simply use the Value property of the combo box. If an item in the combo box is selected then the Value property returns the corresponding value for that item. If no item is selected, then Value returns an empty string.

Ray

[Ray Konopka]

Hi Marcos,

I apologize for the delay in responding. The short answer to your question is that you cannot filter CodeSite messages at the Dispatcher based on message type. You can filter messages based on Category at the Dispatcher level, but that is typically used once in a while in situations where filtering is needed but it is not possible to filter the messages at the program level.

Instead, most developers will filter the messages that get “sent” by CodeSite by creating multiple CodeSite loggers for use their applications. For example, one might create a csCritical logger (with its Category property set to Critical) that is always Enabled. That way, any CodeSite message sent by csCrtical will get dispatched to the destination. Other loggers might be named csDebug, csDevelop, csExternal, csCommunication, etc.

With the various loggers in place, developers simply use the appropriate logger to capture information. Moreover, many CodeSite users will provide a mechanism to enable/disable the various loggers used in their apps. This could be done through INI file settings, Registry entries, XML config files, etc.

Therefore, to control the amount of information generated by an app is handled by configuring the app and not by restricting the messages that are dispatched by the Dispatcher. Also, by using Categories, you can focus on the content of your CodeSite messages and not an arbitrary logging level for the message.

And finally, in order to update the Dispatcher settings, you need to have Admin rights. You can either start the Dispatcher as an Admin, or you can run the CodeSite Controller as an Admin at you will then be able to change the Dispatcher settings.

Ray

[Author]

Posts