Lajos Juhász

You should define your view in Tools -  Options. You can find it if you navigate to User Interface - Form Designer - Device Manager or just write Device manager into the search edit box at the top. 

https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Adding_a_Device_Preset

My only experience with this kind of debugging is that it's going to result a request time out.

46 minutes ago, FPiette said:

Is Delphi-Praxis written in Delphi or PHP or something else ? Is it a standard product or whatever ?

Hint: Powered by Invision Community.

I cannot fully understand the question either. My bet is that the TDBgrid for blob fields instead of the value displays (Memo). In order to correct that a solution is to use  the OnGetText event of the TMemoField/TWideMemoField:

Quote

procedure TForm3.FDQuery1MyMemoFieldGetText(Sender: TField; var Text: string; DisplayText: Boolean);
begin
  if DisplayText then
    Text:=Sender.AsString;
end;
 

3 minutes ago, Uwe Raabe said:

Relying on unit scope names also makes the compiling slower.

For me it made unstable. There was no chance to do compile all for a large project group. The solution was to add scopes to unit names and improve code structure and reduce circular references.

For me MMX Code Explorer works perfectly to reduce circular references (Unit dependency Analyzer). For compiler stability possible it's more important to write the entire unit name eg. Winapi.Windows instead of Windows and having a large list of unit scopes names in the options. 

I cannot help here. If you're going to feel better I have similar issues with auto generated SQLs on Informix. My solution is to generate SQL in my code and don't rely on auto generated statements.

7 hours ago, Bart Kindt said:

I cannot see it anywhere in the Android documentation. I must be looking at the wrong place...

Most probably you're looking at wrong place: https://developer.android.com/training/location/permissions

You have to download the Windows SDK and use the signtool. (https://learn.microsoft.com/en-us/windows/win32/seccrypto/using-signtool-to-sign-a-file).

Your report has a status Open. It's not rejected (yet).

I can confirm using both OnClick and OnChange events that I can receive:

45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
45113
-700000
 

28 minutes ago, bravesofts said:

last question:

is it impossible to create threads in mobile devices while avoiding the main app thread from going to the next line of code until tasks complete ?

No. The reason to create a thread is to move to the next line without waiting for a block of code (inside the thread) to complete.  That's the purpose for threads in every platform.

6 minutes ago, bravesofts said:

I'm afread again :

Delphi does not support background threads in Android and iOS devices where the main thread wait smoothly and safe... 

On the other hand I believe you should learn a bit more about multi threading.

4 minutes ago, bravesofts said:

Is there a safe solution to block the main thread smoothly without freezing the app while waiting our task to complete "using the right task way above.. " Especially in mobile devices

On mobile devices you should never block the main thread (or risk that the OS will terminate your program).

Without more details we cannot help you. Most probably you want to disable the UI elements that are not allowed while your background thread is executing. 

19 minutes ago, bravesofts said:

Delphi does not support background threads in Android and iOS devices !!

https://blog.marcocantu.com/blog/2014_may_background_delphi_android_threads.html

Thank you pyscripter for the enormous work on synedit.

you can ask AI to write this code. An anser from Bing

function IsSundayBetween(StartDate, EndDate: TDateTime): Boolean;
var
  Day: TDateTime;
begin
  Result := False; // assume there is no Sunday between the dates
  Day := StartDate; // start from the start date
  while Day <= EndDate do // loop until the end date
  begin
    if DayOfWeek(Day) = 1 then // check if the day is Sunday
    begin
      Result := True; // set the result to true
      Break; // exit the loop
    end;
    Day := Day + 1; // increment the day by one
  end;
end;

there is an open RSP - https://quality.embarcadero.com/browse/RSP-39793.

13 hours ago, James Steel said:

Thanks for the additional suggestions. It is very strange that no changes had been made when the stock overflow errors started. Some file may have become corrupted. It would be great if there were a better way to debug the problem rather than starting over and re-installing all the third-party components.

There is one acient technique: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Testing_Installed_Components

https://stackoverflow.com/questions/25843845/how-to-have-delphi-twebbrowser-component-running-in-ie9-mode

5 minutes ago, PeaShooter_OMO said:

How would this code behave differently between Debug and Release? Do both compile?

My guess is different memory layout in debug and release mode. That's why the code inserted to debug changed the behaviour of the bug.

If you enable Runtime Themes you delegate the drawing for some components to Windows and the colors from the Active Windows Theme is used. In ancient versions of Delphi this was done through XPManifest.

You can use VCL Styles to customize the drawing.

var x: real;
begin
  SetExceptionMask(exAllArithmeticExceptions);
  x:=0/0  ;
  showmessage(FloatToStr(x));

Most probably some dll changes the exception mask.

10 minutes ago, Fr0sT.Brutal said:

Why not just do FindFirst(root+pattern) where pattern could be either mask or exact name?

One possible reasould could be that FindFirst would not return subfolders that doesn't match the pattern.

If agree there are bugs for example (SR.Attr and faDirectory) = SR.Attr should be (SR.Attr and faDirectory) = faDirectory

Your code is working for me.  A note that you're leaking memory findfirst will allocate some memory and that must be released with FindClose(SR). Also you should never write Form1.Listbox1.