Ray Konopka

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 306 total)
  • Author
    Posts
  • in reply to: Delphi 7 Compatible Raize Components #3555
    Ray Konopka
    Keymaster

      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

      in reply to: Out of memory errors #3516
      Ray Konopka
      Keymaster

        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

        in reply to: Quality Central voting #3515
        Ray Konopka
        Keymaster

          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
          Keymaster

            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
            Keymaster

              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

              in reply to: Problem with RZLabel (BlinkIntervalOn) #3490
              Ray Konopka
              Keymaster

                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

                in reply to: Out of memory errors #3489
                Ray Konopka
                Keymaster

                  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

                  in reply to: SendCollection method #3485
                  Ray Konopka
                  Keymaster

                    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

                    in reply to: Problem with RZLabel (BlinkIntervalOn) #3480
                    Ray Konopka
                    Keymaster

                      Hi Gabriel,

                      The blinking support in the TRzLabel and TRzStatusPane utilizes a common control list that wraps a TTimer that controls the blinking on and off. There are two primary reasons why this was done. First, only one timer is needed instead of having a separate timer for each label. Second, it allows all labels that are blinking to blink at the same rate and more importantly that the blinking is synchronized.

                      To use a different blinking interval for a label on a separate form, then I would suggest dropping a TTimer on the form and manually blink the desired label by changing the color.

                      Ray

                      in reply to: F2084 Internal Error: URW8074 #3470
                      Ray Konopka
                      Keymaster

                        Hi Harald,

                        The easiest solution is to upgrade your Delphi 11.2 version to 11.3. After doing so you will then download the KSVC from GetIt, which is built for 11.3.

                        If you need to stay with 11.2, then you have a couple options. You could try running the !Build_RC6.cmd file that is located in the KSVC Source directory. You’ll need to follow the instructions at the top of the batch file to verify the Delphi version and compiler location. After editing the !Build_RC6.cmd file, you can then run it to rebuild the components using the Delphi compiler installed on your computer. The batch file will then copy the new *.DCU files to the correct location.

                        Another option is to add the KSVC Source directory to your Library Search Path (or Project Search Path) so that the compiler rebuilds the component source code. Then, when you build your project, the KSVC components will get recompiled.

                        The crux of the problem with 11.2 is that there is something wrong with the GetIt distribution that Embarcadero created for KSVC for 11.2. Specifically, one or more DCUs file distributed with KSVC for 11.2 are corrupted in some way. I am aware of the RzBorder.dcu file, but there could be others.

                        Ray

                        in reply to: Method indentation problem #3469
                        Ray Konopka
                        Keymaster

                          Hi Ariagna,

                          The key to handling this situation is to add a Reset Separator to the message log. In the situation that you described above, after forcibly terminating your app with Task Manager, go to the Live Viewer and select Edit > Add Reset Separator. (There is also a toolbar button that does the same thing). The reset separator appears as 2-line separator and resets the indentation level.

                          You can also programmatically add a reset separator by calling the AddResetSeparator method from a CodeSite logger.

                          Ray

                          in reply to: F2084 Internal Error: URW8074 #3461
                          Ray Konopka
                          Keymaster

                            Hi Marc,

                            Have you tried rebuilding with 11.3? There is also a new version of KSVC for 11.3 that was released.

                            Ray

                            in reply to: TRZFormState and HDPI #3460
                            Ray Konopka
                            Keymaster

                              Hi Andrew,
                              Sorry for the long delay. I missed your last response. The TRzFormState connects to a TRzRegIniFile which can save settings to either the Registry or an INI File.

                              Ray

                              Ray Konopka
                              Keymaster

                                Hi David,

                                I created test a project that I think may help explain things a bit. I dropped two TRzButton controls (btnLaunch and btnContinue) and a TRzLauncher onto the form. I also created a new enum called TAppState and created a corresponding private field, FAppState, to keep track of the current state of the app. The TRzLauncher has its FileName property set to ‘C:\Windows\Notepad.exe’. When the app starts, FAppState defaults to appInit. The btnLaunchClick event handler looks at the FAppState field and only launches Notepad if FAppState is not equal to appWaiting. Before calling RzLauncher1.Launch, FAppState is set to appWaiting.

                                The btnContinueClick event handler also looks at the FAppState field, but only calls ShowMessage if the state is appContinue. The FAppState field is set to appContinue in the OnFinished event handler.

                                When you start the app, clicking the Continue button does nothing since FAppState is appInit. Clicking the Launch button launches Notepad. While Notepad is running, clicking Launch or Continue does nothing. Once Notepad is closed, then clicking Continue will show the message box.

                                The point is that it is not necessary to do any looping to accomplish what you want. In fact, it is the looping (in the UI thread) that is forcing you to call Application.ProcessMessages.

                                Ray

                                unit Unit26;
                                
                                interface
                                
                                uses
                                  Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
                                  Vcl.Controls, Vcl.Forms, Vcl.Dialogs, RzButton, RzLaunch, Vcl.StdCtrls, RzLabel;
                                
                                type
                                  TAppState = ( appInit, appWaiting, appContinue );
                                
                                  TForm26 = class(TForm)
                                    btnLaunch: TRzButton;
                                    RzLauncher1: TRzLauncher;
                                    btnContinue: TRzButton;
                                    procedure btnLaunchClick(Sender: TObject);
                                    procedure btnContinueClick(Sender: TObject);
                                    procedure RzLauncher1Finished(Sender: TObject);
                                  private
                                    { Private declarations }
                                    FAppState: TAppState;
                                  public
                                    { Public declarations }
                                  end;
                                
                                var
                                  Form26: TForm26;
                                
                                implementation
                                
                                {$R *.dfm}
                                
                                procedure TForm26.btnLaunchClick(Sender: TObject);
                                var
                                  J: integer;
                                begin
                                  if FAppState <> appWaiting then
                                  begin
                                    FAppState := appWaiting;
                                    RzLauncher1.Launch;
                                  end;
                                end;
                                
                                procedure TForm26.btnContinueClick(Sender: TObject);
                                begin
                                  if FAppState = appContinue then
                                  begin
                                    ShowMessage( 'Allowed to Continue' );
                                  end;
                                end;
                                
                                procedure TForm26.RzLauncher1Finished(Sender: TObject);
                                begin
                                  FAppState := appContinue;
                                end;
                                
                                end.
                                in reply to: TRZFormState and HDPI #3434
                                Ray Konopka
                                Keymaster

                                  Hi Andrew,

                                  Since acquiring the components back in 2015, Embarcadero has addressed some HDPI-related issues in the components, but unfortunately there are still outstanding issues. Such as what you describe with TRzFormState. I would encourage you to submit a report on Quality Portal about this issue so that Embarcadero becomes aware of the issue and can track it, and hopefully address it. Please prefix the title of the report with “KSVC:” as request by Marco Cantu.

                                  Ray

                                Viewing 15 posts - 46 through 60 (of 306 total)