Jump to content

Uwe Raabe

Members
 View Profile  See their activity

  • Content Count

    2558

  • Joined

  • Last visited

  • Days Won

    150

Posts posted by Uwe Raabe

  1. Posted 

    program Project458;

{$APPTYPE CONSOLE}

{$R *.res}

uses
  System.SysUtils,
  System.TimeSpan;

var
  span: TTimeSpan;
begin
  span := TTimeSpan.Subtract(EncodeDate(2018,1,2)+EncodeTime(16,35,0,0), EncodeDate(2018,1,1)+EncodeTime(15,30,0,0));
  Writeln(Format('%d Day(s) %d Hour(s) %d Minute(s)', [span.Days, span.Hours, span.Minutes]));
  Readln;
end.

     

    • Like 1

  2. Posted

    1 hour ago, FPiette said:

    I'll be more than happy to have MMX :: Source Indexer window remember his position and size each time it is reopened. it is a real pain to have it always opened in the top left corner of the screen with his default position and size.

    Are you aware that the Source Indexer window is part of the desktop and thus stored with it? You can move it wherever you want or dock it to a suitable place, save the desktop and it is restored whenever the desktop is loaded again. The position is also stored in the desktop when the Source Indexer is not visible anymore while saving. I know this is not the same as storing the last position, but unfortunately both storage mechanisms don't play together nicely.

     

    The other suggestions are in the issue tracker now.

  5. Posted

    33 minutes ago, Rollo62 said:

    Maybe Uwe's MMX-Explorer might be a helpful tool clearing your units up.

    (be aware, I'm not sure if its already 100% Rio-ready yet, better check before)

    There is a beta for Rio as announced in this thread: https://en.delphipraxis.net/topic/287-mmx-for-delphi-103-rio/

     

    Although there are still some minor glitches (e.g. using the v13 registry key than the v14 one), it seems to work quite reliable. When I find some time during the next days I will provide an official release.

     

    BTW, the Use Unit dialog of MMX allows to add predefined modules, which are just groups of unit names. Click the small wizard symbol to the right from the edit field. This is quite helpful when you have to add several units that somehow belong together and are often needed in full.

    • Like 1

  6. Posted · Edited by Uwe Raabe

    7 minutes ago, Stéphane Wierzbicki said:

    I'm using Delphi for almost 2 decades and never got such issues.

    These procmon entries have nothing to do with the unresponsiveness you see. 

     

    3 minutes ago, Attila Kovacs said:

    Maybe I need glasses, it's desired access not denied, but this doesn't explain why are you telling us "fresh install" and why can't bds find anything.

    As Stefan said: The IDE tries to resolve unit scope names and the resulting filenames simply don't match any existing file - so no access can be granted. This is normal behavior since quite a couple of Delphi versions.

  9. Posted

    6 minutes ago, Sherlock said:

    And I would identify the type behind @SomeArray[SomeStructure.SomeIndex] which you would have to do for that typed pointer you're using anyway and gotten a variable of that type.

    That would work for classes, but fails for records. Introducing a record variable will give you a copy of the array element for your changes. The original array element will stay unchanged.

     

    A valid alternative would be a record method like SetBlaBlub(5, 10) which directly manipulates the underlying record. This might even benefit the readability.

    • Like 1
    • Thanks 1

  13. Posted

    1 minute ago, PeterPanettone said:

    As I already said, this is not possible.

    So then you probably have to live with the scaling bugs until 10.4, where High-DPI support for the IDE is on the roadmap. We can only give hints and tips here - we cannot fix the IDE for you.

     

    On the other hand does 10.3 work perfectly here on a 4k monitor set to 200%. The difference to your setup may be that I have three monitors where monitor 1 and 2 are set to 100% and only monitor 3 to 200%. As the default DPI for Windows is taken from monitor 1 and thus 100%, this may lead to the correct display even for 200% I can see on my system.

     

    Following this logic, I repeat my suggestion to set your DPI setting to 100% - for your system DPI - on an additional monitor. Then you can have your HiRes monitor set to a higher DPI and hopefully don't see that scaling bugs anymore. Perhaps you can try it.

    • Like 1

  18. Posted

    35 minutes ago, Primož Gabrijelčič said:

    Just ... with ... brrrr, terrible.

    Interestingly, that is quite similar to one of the reasons why "with" was invented in the first place: when accessing the record memory is costly. From Pascal User Manual and Report (emphasizes by me):

     

    Quote

    The with clause effectively opens the scope containing field identifiers of the specified record variable, so that the field identifiers may occur as variable identifiers. (Thereby providing an opportunity for the compiler to optimize the qualified statement.)

     

    • Like 3

  19. Posted

    Drag-Select all the text you want to quote and click on the little "Quote" hint appearing when your selection is finished.

     

    That is also a good way to quote only part of a post and I miss that feature already in the German forum.

    • Thanks 1
×