Jump to content

Uwe Raabe

Members
  • Content Count

    2542
  • Joined

  • Last visited

  • Days Won

    147

Posts posted by Uwe Raabe


  1. 25 minutes ago, alogrep said:

    that "the vast majority had no problems with this update" is of no sonsolation to me.

    Yes, I know that. My comment was more about a global experience, while the individual case may deviate. Because the failure cases are rare, providing a ready to use solution just lacks the necessary data. I already mentioned the GetIt thing, that helped others. Unfortunately each case seem to be somewhat different.

     

    IMHO you have two options now:

    1. Either try to investigate the underlying cause of your problems and try to fix them or
    2. remove everything and install it from scratch. The depth of the "remove everything" may influence the outcome. If even that doesn't help, there may be something special with your system. If you have the chance to make an installation on a fresh system (f.i. VM) you should try that first.

    If you opt for the first option, I suggest to start the IDE with a new registry key. That allows to skip all user specific components and settings, but keeps the all user ones.


  2. 1 hour ago, programmerdelphi2k said:

    my prefere is always a "new fresh install", but others using the "updating" as expected

    An "Update" from 11.2 to 11.3 is internally an uninstall followed by an install. Unless explicitly told this procedure keeps the registry settings intact as well as the license information. A "new fresh install" may only be possible with a clean machine which has seen no Delphi ever.

     

    To me, identifying the actual problem and taking actions to fix that seem a more productive approach to me on the long run. Otherwise we will see people struggling with this forever.

     

    BTW, the vast majority had no problems with this update. It is just that we don't hear from them.


  3. 4 minutes ago, Bbommel said:

    How do I get this precompiled dcu the best way?

    When compiling the packages set dedicated DCU output folders for RELEASE and DEBUG. Then compile the packages first with DEBUG configuration and after that with RELEASE configuration (the other way round would make you work with DEBUG packages in the IDE). Then copy all DFM and RES files from the sources to the RELEASE DCU folder.

     

    In your Project Options replace the Search path to the SVG sources with the RELEASE DCU folder from above in the BASE configuration and add the DEBUG DCU folder in the DEBUG configuration. That way the debug dcus are found before the release dcus, while the resource files are still taken from the release folder.

     

    To make the debugger find the source files, select Debugger in Project Options, switch to the DEBUG configuration and add the source folder you just replaced to Source Path.

     

     

    • Like 2

  4. I found that hint also annoying, especially as some people tend to have no hints and warnings when building their projects. IMHO it would be sufficient to emit it only f.i. in DEBUG mode or even better controlled by a specific DEFINE.

     

    As a workaround you can pre-compile the component units and use only the DCUs for your projects. As you stated, you prefer not to change the code, you can as well go this way - it will even speed up compile time a bit. That doesn't hinder you to debug the sources as long as everything is set up properly.

    • Like 1

  5. 1 hour ago, David Heffernan said:

    That's the scenario I have, with multi select enabled. And yes I walk the entire list checking selected state for each item. 

    I wonder if OnSelectItem alone works when selection is done by Ctrl-Click or Ctrl-<cursor keys>. In one of my applications I had to wire OnDataStateChange, too. Without that I missed some notifications to react on selection changes.


  6. 3 hours ago, Manlio Laschena said:

    [dcc32 Fatal Error] F1030 Invalid compiler directive: '-AC:\Users\manli\Documents\Lavori\Projects\2023\Test\InputQuery\;Generics.Collections=System.Generics.Collections;Generics.Defaults=System.Generics.Defaults;WinTypes=Winapi.Windows;WinProcs=Winapi.Windows;DbiTypes=BDE;DbiProcs=BDE;DbiErrs=BDE'

    This looks like a bad Unit Alias entry in the Debug configuration. Open the Project options and select Delphi Compiler. Check the Unit Alias entries for the different build configurations. You may spot the path name somewhere, which may be entered there instead of into the Search Path entry.

×