Uwe Raabe

AFAIK, CodeSite is limited to Windows, probably even VCL only. Apart of that it is really great.

This is another approach without any loops: function CalcSundaysBetween(StartDate, EndDate: TDateTime): Integer; begin var D1 := Trunc(StartDate); var D2 := Trunc(EndDate); if D2 < D1 then begin var tmp := D1; D1 := D2; D2 := tmp; end; var offset := (D1 + 6) mod 7; Result := (D2 - D1 + offset) div 7; { check if lower date is a Sunday } if offset = 0 then Inc(Result); end; BTW, despite the title says, according to the examples in his post the OP seems to be more interested in the number of Sundays instead of just their existence.

How do you want to handle the case when both dates are equal as well as a Sunday? How, if they are not equal and both are a Sunday?

Well, at least RADServer is available for Linux.

What is your definition of a "REST framework"?

Remove seFont from the StyleElements property.

Only for WARN: Warning messages (Delphi)

Yes, it obfuscates what it is doing.

TImageCollection holds several Images, where each can have multiple sizes, which renders THE size of an image meaningless. You need to inspect the SourceImages of the Image returned by the collection to get the available sizes. Only if the image has just one SourceImage there also is only one size.

You might get away with some hard casting then: TempInt := Int16((UInt16(TempInt) and $FFFC) or (_Invalids and $03)); I wonder if simply disabling range checks for the whole routine would be the best solution here.

I also cannot see a problem with multiplying -2048*11 in a signed 16-bit integer either.

Does anyone have gender statistics for this forum at hand? What is the percentage of female users here?

I customized my Welcome Page to get rid of everything accessing the Internet. That works quite well now.

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: Either try to investigate the underlying cause of your problems and try to fix them or 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.

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.

It is more that there are several of those.

I guess, whatever the real intention is, one can always make up a fake reason to do so.

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.

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.

Some people found it helpful to manually uninstall all GetIt packages before the update and re-install them afterwards. The installer seems not to handle that very well by itself.

For reference see Platform-dependent integer types

I didn't try, but you might succeed with just using Winapi.GDIPOBJ.pas. It calls GdiPlusStartup when not inside a DLL.

Unfortunately that removes a couple of other features from your app.

Then the error is most likely located inside that code.

Does it work when you omit doStuff?