Jump to content

Uwe Raabe

Members
  • Content Count

    532
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by Uwe Raabe

  1. Uwe Raabe

    MMX for Delphi 10.3 Rio

    I am already investigating that. Unfortunately I cannot reliably reproduce it here.
  2. Indeed! After trying several other approaches I reverted my build machine back to 10.3.1 to provide a compatible version. Believe me, I am not amused - to say the least.
  3. For an IDE package to work in Delphi 10.3, 10.3.1 and 10.3.2 it has to be compiled with 10.3 or 10.3.1 in the first place. The compatibility patch is needed to make such an application work with 10.3.2 (actually the patch is meant for 10.3.2 installations only). There is no way to make a package compiled with 10.3.2 work with 10.3 and 10.3.1. This case is a bad combination of first breaking compatibility by accident and then refuse to fix it because that would break some other compatibility.
  4. Uwe Raabe

    Delete a Registry Key...

    Highlight the text with the mouse and click on the then appearing Quote bubble:
  5. Uwe Raabe

    TFDMemtable does not save indexdefs definitions

    AFAIK, IndexDefs (as well as FieldDefs) are stored in the DFM when StoreDefs is True, but I guess they are not part of the data file.
  6. Uwe Raabe

    MMX 15 (Beta) Available

    There is a new beta available. Changing the version number to 15 resembles not only the completely different new look due to theme support and new icons, but also the internal changes necessary to make all this work. Hopefully I didn’t break too much.
  7. Uwe Raabe

    MMX 15 (Beta) Available

    OK, I found why I thought the problem to be fixed: It happens only under some complex conditions which were not always satisfied in my test configuration.
  8. Uwe Raabe

    MMX 15 (Beta) Available

    Indeed. Not sure what scenario I tested then. I am also wondering what Unit Dependency Analyzer has to do with it.
  9. Uwe Raabe

    Delete a Registry Key...

    Seems like the docs are mistaken here. The source code is more reliable and shows that subkeys are internally deleted.
  10. ArcTan2 produces the same result when both of its parameters are multiplied with the same factor. Thus dividing both by cnt before calling ArcTan2 has no influence on the result. In addition, ArcTan2 is pretty well capable of handling some special values like c = 0 (at least in non-ancient Delphi versions). There is no need to catch this case in advance.
  11. Uwe Raabe

    With's the deal with "With"?

    This is a quote from Knuth's C adaptation of the original Adventure game by Will Crowther:
  12. Uwe Raabe

    VCL-styled Popupmenu issue if imagelist is assigned

    Unfortunately some companies insist on having their corporate styling being reflected in their applications. Just because some colors are different from the Windows standard doesn't mean that one needs to learn how to use that UI. That is more related to uncommon handling of TAB vw. ENTER keys or the misuse of well known shortcuts.
  13. Uwe Raabe

    VCL-styled Popupmenu issue if imagelist is assigned

    Looks like this issue: Bug In popupMenu with VCL Style - fixed in 10.3.2
  14. Uwe Raabe

    IDE changes monitor when debug run

    As there seem to be people with different expectations, it would be best to make that configurable: Selecting Layout doesn't remember which monitor a form is on
  15. While working on a tool for cleaning up uses clauses I stumbled upon this beast (slightly changed to protect the innocent): {$if defined(DEBUG) or defined(DEBUG_SPECIAL)} uses {$ifend} {$IFDEF DEBUG} dialogs {$ENDIF} //<some comment about the following ifdef> {$IFDEF DEBUG_SPECIAL} mmsystem, // timeGetTime() messages {$ENDIF} {$if defined(DEBUG) or defined(DEBUG_SPECIAL)} ; {$ifend} If you are only looking for uses clauses inside some Delphi sources and try to avoid a full featured parser, you will have a pretty hard job to detect, parse and interpret that one correctly. So, if you are interested to make any use of such a tool, please do me a favor: Don't write your code that way! It is hard to read for humans anyway.
  16. Uwe Raabe

    No marker for modified source files

    At least that is much easier now than with these older Delphi versions.
  17. Uwe Raabe

    [Firedac] Connection Pooling

    While this may suit a single threaded application, the pooling approach is the recommended way for multi-threaded DB access. http://docwiki.embarcadero.com/RADStudio/Rio/en/Multithreading_(FireDAC)#Connection_Pooling
  18. Uwe Raabe

    No marker for modified source files

    Known issue: No visual marks of modified files
  19. Uwe Raabe

    Ide Rio: "Compile" not only one project

    That is not the usual behavior. There must be something special in your installation. Can you provide detailed steps?
  20. Uwe Raabe

    Line numbers in code editor

    Tools > Options > User Interface > Editor Options > Display > Number All Lines http://docwiki.embarcadero.com/RADStudio/Rio/en/Display
  21. Uwe Raabe

    Ide Rio: "Compile" not only one project

    As I never had such an issue, I simply cannot tell. Perhaps creating a new dproj for each project affected helps.
  22. Uwe Raabe

    Ide Rio: "Compile" not only one project

    It is not a general problem with the IDE. Otherwise I wouldn't be able to work efficiently any more. When there is nothing suspicious in the groupproj file, it might be something special in the dproj files.
  23. Uwe Raabe

    [Firedac] Connection Pooling

    Perhaps you are missing this line after the call to AddConnectionDef? FDManager.Active := true;
  24. Uwe Raabe

    Resolve a uses clause unit path?

    Are you aware of this function from IOTAServices? { ExpandRootMacro will change a string that contains $(BDS) or any $(name) and expands that environment variable. So for example $(BDS)\bin will be expanded to C:\Program Files\Embarcadero\10.0\bin assuming that BDS=C:\Program Files\Embarcadero\10.0 } function ExpandRootMacro(const S: string): string;
  25. Uwe Raabe

    On The Design Of Uses Clauses

    If you can provide reproducible test cases, you should send them to Peganza. They are always interested in cleaning out those glitches.
×