Jump to content

Uwe Raabe

Members
  • Content Count

    2839
  • Joined

  • Last visited

  • Days Won

    168

Everything posted by Uwe Raabe

  1. Uwe Raabe

    OnMTUChanged Event in 12.3

    One possible scenario: Product Management schedules RSP-38842 for 12.3 Product Owner assigns the task to implement that to some developer Developer implements it in an interface breaking way Developer team realizes that the change cannot be done in 12.3 and postpone merging the change Unfortunately they forgot to notify the Product Owner to adjust the fix version
  2. Uwe Raabe

    OnMTUChanged Event in 12.3

    It looks like a mistake when writing these release notes. A new event would be an interface breaking change and thus cannot (should not) be implemented in a point release. Most probably this will make it into Delphi 13.
  3. Uwe Raabe

    OnMTUChanged Event in 12.3

    Can you point to the comment you are referring to?
  4. Uwe Raabe

    Has the toolbar problem been fixed?

    Yeah, I know. That's a pity...
  5. Uwe Raabe

    Has the toolbar problem been fixed?

    A stable Delphi is also important to me. That's why I do my best to help Embarcadero achieve this.
  6. Uwe Raabe

    Has the toolbar problem been fixed?

    There are several toolbar issues listed as fixed in 12.2.
  7. It doesn't happen here and at least I cannot remember having this seen anytime. As usual: Can you reproduce with a vanilla IDE installation?
  8. Uwe Raabe

    Ho to list all data-aware controls attached to a datasource

    You can iterate the protected DataLinks property (there are several ways to access a protected property described elsewhere). For each TDataLink in this list act according to the actual class type: A TFieldDataLink gives you access to the corresponding Control, while a TGridDataLink provides the connected Grid. There are other classes inherited from TDataLink with other purposes, but that should you get started.
  9. Uwe Raabe

    Is this a change in 12.3??

    Make sure that the query is not Active in the designer.
  10. Uwe Raabe

    formatting private const identifier = value

    Are you aware that your second example won't compile? It needs an additional var keyword between the constant declaration and the following field declaration.
  11. IMHO, it absolutely makes no sense to issue a warning about an Unsafe typecast of <mytype to <mytype>, when neither these are different types nor any type cast is done at all (let alone one being unsafe). The most matching issue in QP is probably this one: https://quality.embarcadero.com/browse/RSP-30869. Given that it seems to be fixed, there may be a good chance that the current failure will be fixed, too.
  12. IMHO, this warning is just bogus and it shouldn't be emitted in the first place. So the usual way would be to file a bug report to fix the compiler. Unfortunately there already exist a couple of issues about this warning and Embarcadero seems to prefer to ignore them because this warning is off by default and they see no sense in activating them. (Not that I would actually support this solution.) In case you need to keep these warnings active, you might consider wrapping all occurrences in {$WARN UNSAFE_CAST OFF} ... {$WARN UNSAFE_CAST DEFAULT}
  13. Uwe Raabe

    About the compiler (not) finding the DFM files

    It is basically what the IDE does to support the entries in the configurations. So, yes, that will work. Actually, it matches my proposal a few posts above.
  14. Uwe Raabe

    function declarations without ; at the end

    I found the first entry of this function in Delphi 2010 and it misses the semicolon already.
  15. Indeed there are: Set TControl.RaiseOnNonMainThreadUsage := True This will raise an EInvalidOperation when CheckNonMainThreadUsage is called for a control. This is automatically done inside CreateWnd.
  16. Uwe Raabe

    How I fixed LSP (sorta) and a question

    Shall I read that as we made changes to the interface part? Interesting. A short test on my system showed that it was not possible to navigate to any VCL source file when the $(BIN)\source\VCL entry of the browsing path was missing. It's probably not me alone who would be interested in a reproducible test case.
  17. After installing the patch most of the packages compiled with the unpatched version must be re-compiled to work with the patched version.
  18. Uwe Raabe

    function declarations without ; at the end

    Wrong! According to N.Wirth (Pascal User Manual and Report page 149) there is an Empty Statement:
  19. Uwe Raabe

    About the compiler (not) finding the DFM files

    Create an Option Set with the appropriate entries and add that to each project as reference. Then you really have only one place to change that even works when the project is opened in an IDE using another registry key, being another version or residing on a different system - all assuming that the paths actually exist. Personal preference and the fact that I work for different customers with different sets of used libraries. I just don't want to clutter the search path with unneeded entries.
  20. Uwe Raabe

    function declarations without ; at the end

    In Pascal the semicolon is a statement separator and not part of the statement. Remember the if-then-else...
  21. Uwe Raabe

    About the compiler (not) finding the DFM files

    My request is targeting the per project option on purpose, while the global option would probably make sense, too - in addition. Please feel free to add your opinion on that in the comments, best with a concrete example where the current state may fail. Perhaps this per project approach is driven by my personal favor of not contaminating the library path with the paths from the installed components, but add these on a per project basis restricted to the libraries actually used by the project. My projects follow a common folder pattern with a source and a lib folder at the project root and all libraries as sub folders of lib. This allows for similar relative paths in each project to find all the library files.
  22. Uwe Raabe

    How I fixed LSP (sorta) and a question

    Wouldn't it be sufficient to adjust the entries in Tools > Options > Language > Delphi Options > Library -> Browsing path?
  23. Uwe Raabe

    About the compiler (not) finding the DFM files

    RSS-3125: Add Option to edit DCC_ResourcePath
  24. Uwe Raabe

    Delphi 12.3 is available

    The actual wording is: If that means replacing the current system with a completely new approach is debatable.
  25. Uwe Raabe

    About the compiler (not) finding the DFM files

    Not quite, that setting is stored as BRCC_IncludePath. DCC_ResourcePath is indeed the correct way to provide the paths to look for the DFM resources. Unfortunately there is no UI to edit that. Manually editing the dproj file adding a node like <DCC_ResourcePath>..\lib\Source;$(DCC_ResourcePath)</DCC_ResourcePath> under the appropriate PropertyGroup will make the DFM files located in ..\lib\source to be found without exposing the PAS files in that folder.
×