Jump to content

Uwe Raabe

Members
 View Profile  See their activity

  • Content Count

    2545

  • Joined

  • Last visited

  • Days Won

    147

Posts posted by Uwe Raabe

  6. Posted

    1 hour ago, Remy Lebeau said:

    There is nowhere you can "put the app" that will make the OS run your app during sleeps/wakeups.

    You could execute the app with a Windows Task Scheduler event triggered by the different conditions. The tricky part is to find the appropriate event ids, where The Kernel-Power Event Provider can be helpful. It also is possible that the app doesn't get the time to execute its task before the system goes to sleep and finishes it after waking up.

  9. Posted

    Sorry, that is only an excuse to not report bugs. It will only lead to the ability to lament on bugs not being fixed, while the reason they are not fixed is not being reported in the first place.

     

    While there indeed exist bugs that are not fixed in decades if ever, there are a lot more being fixed only because they were reported. F.i. my statistics list 145 reported bugs, from whom 30 are still open, while only 8 were closed as Works as expected.

     

    Reporting bugs is necessary for having them fixed - it may not be sufficient, but it just is necessary!

     

    So let me quote Thomas here:

    49 minutes ago, dummzeuch said:

    If nobody files a bug report, there will be no fix.

     

  12. Posted

    23 minutes ago, Gary said:

    I could not get Embarcadero to do it no matter who I talked to.

    If that is indeed the case you should escalate this until you succeed. This would be the first case where Embarcadero actually denies the bump even when the request was made through the required channels.

     

    I have been involved in a couple of cases in the German Delphi-PRAXiS where the hint contacting Embarcadero Germany was sufficient to get it done. I don't know which sales office is responsible for your case, but I suggest pestering them on and on to get this straight.

  14. Posted

    Although it has been mentioned before: The license isn't invalidated after subscription has run out. It keeps working and it can even be installed on another system. In case the installation counter needs to be bumped one has to contact Embarcadero Sales (in contrast to Support while on subscription) to get this increased. I have not heard of anyone where that has been denied.

    • Like 3

  16. Posted

    57 minutes ago, Sherlock said:

    sadly it did not take flight.

    Indeed, a bit sad. I still have hope that this will get some traction shortly.

     

    It might be worth to know that a fork of that repo, namely https://github.com/UweRaabe/Delphi-Unit-Tests, is actually part of the regression tests run by Embarcadero. It also has a couple of contributors as well as branches, albeit lacking some activity, too.

    • Like 1
    • Thanks 1

  18. Posted · Edited by Uwe Raabe

    The point is that if you want to test for invalid parameters, you have to pass them inside another test method instead of a separate test case.

     

    Currently we have one test method 

    procedure TestAdd(Value1, Value2, _Result: Int64);

    Unfortunately we don't have the implementation, so I have to do a bit of guessing here: 

    procedure TMyTestClass.TestAdd(Value1, Value2, _Result: Int64);
begin
  Assert.AreEqual(_Result, Add(Value1, Value2));
end;

    Whatever is passed to the TestAdd method, the parameters given to the Add method are always valid types.

     

    To test some invalid parameter we need another test method TestAddInvalidParams passing invalid parameters to the Add method. 

    procedure TMyTestClass.TestAddInvalidParams;
begin
  // call Add with some invalid params and chec if it fails
end;

    Passing invalid parameters to TestAdd via a TestCase attribute only tests the capability of DUnitX to detect invalid parameters in a TestCase attribute. It does not test Add to fail with invalid parameters.

     

    BTW, whether you even can pass invalid parameters to Add depends on the declaration of Add which we cannot see.

    • Like 1

  21. Posted

    While Delphi 12 supports ZIP encryption, the actual encryption algorithm has to be provided by the developer itself or a library implementing the new IZipCryptor interface.

     

    For the common PKWARE Zip 2.0 encryption (see APPNOTE.TXT) an implementation can be found in PKWAREZipCryptor.pas. The usage is shown in the following example, which extracts all files from an encrypted zip file: 

    var
  bytes: TBytes;
  fileName: string;
  zipFile: TZipFile;
begin
  zipFile := TZipFile.Create;
  try
    zipFile.Cryptor := TPKWAREZipCryptor.Create;
    zipFile.Password := cPassword;
    zipFile.Open(zipFileName, zmRead);
    for var I := 0 to zipfile.FileCount - 1 do begin
      fileName := zipFile.FileNames[I];
      zipFile.Read(I, bytes);
      TFile.WriteAllBytes(fileName, bytes);
    end;
    zipFile.Close;
  finally
    zipFile.Free;
  end;
end;

     

    • Like 3
    • Thanks 3

  23. Posted

    48 minutes ago, Brandon Staggs said:

    I think it would be more useful if they were to simply remove features that are broken beyond usability and not meant to be fixed.

    AFAIK, the plan was to make Refactoring opt-in, but it came with other regressions when not installed. So they finally made it opt-out.

     

    Anyway. It is commonly known since ages that any 0-release is not made for production. Let's wait for the first hotfix - at least.

×