c0d3r

It said the problem would occurs when using offline installer, but I was using web installer, still my 64bit LIBRARY (Windows) paths were wiped out.

I saw the code in Delphi 10.4.2, but I don't see any forms flickering in Window 10.

Yeah, all my win64 component paths were wiped out. Luckily, I had backup the registry before upgrade, so re-import the registry solves.

I got Kim's emails 3 days ago. Thanks.

@Remy Lebeau I would like to give the codes, but I'm not allow to, they are kbmMW codes, all socket threads related things are done by kbmMW components internally. What we did was just wrote codes in one of its OnRequest event handler to deal with client request by the given request name, and set the return Result. For each request, We made 100% sure to have try--finally--end blocks to have objects created get freed properly, each LockList to has a matched UnlockList to access thread string lists, ..., etc. Anyway, Thanks for your time to anwser all my questions, really appreciated! The codes in ProcessRequest event: @ServiceMethod := MethodAddress(AClientRequestName); if Assigned(ServiceMethod) then begin Result := ServiceMethod(Self, ClientIdent, Args); Handled := True; end; This one of the request codes we wrote (in published section): function TMyService.GetSequenceValue(const ClientIdent: TkbmMWClientIdentity; const Args: array of Variant): Variant; var ds: TkbmMWDataset; SeqName, Step: string; SeqList: TStringList; i: Integer; begin Result := -1; if not PrepareQuery(SEQUENCE_GETVALUE, ds) then Exit; try SeqName := VarToStr(Args[0]); Step := VarToStr(Args[1]); SeqList := FSequences.LockList; try i := SeqList.IndexOfName(SeqName); if i < 0 then Exit; SeqName := SeqList.ValueFromIndex[i]; finally FSequences.UnlockList; end; ds.Query.Text := Format(ds.Query.Text, [SeqName, Step]); ds.Open; if not ds.Eof then Result := ds.FieldByName('ID').AsInteger; finally ds.Free; end; end;

@Remy Lebeau Thanks, I totally agree it. just not sure how to find. Any workarounds we can do? Is there any properties/methods in TidTCPServer that can let all these socket threads being terminated gracefully before calling FSocket.Active := False;

Sorry, I didn't make it clear. its the kbmMWTCPIPIndyServerTransport that use its FSocket: TidTCPServer, to handle everything using some private/protected/public methods, including Execute event. e.g. TransportServer.Listen -> FSocket.Active := True; TransportServer.Close -> FSocket.Active := False;

No Disconnect/StopListen method, only Listen and Close, and the codes were there for 10+ years since 2007, people who use our old app (built with Delphi 2007, Indy 9) are still working great. Its those people who upgraded to our new app (built with Delphi 10.4.1, Indy 10) are having the issue.

As usual I sent email to Kim last week, no response. Wish me luck if I get response. Try registrating to its forum to ask questions, nope, my work email was used and can't register, try 'Forgot/Lost Password' link, Oops, your email doesn't exist. I sent email to Kim about registration issue on Sunday, lets see when I would get the response, so far no any response. EDIT: Oh, Oh, the only email I can always get from him was the email that asking me to pay the annual subscription fee on due date.

Here was what I found tonight on one of our customers server: While stopping the service and timeout, there was a remote connection to the port that having FIN_WAIT_1 status (using netstat -a), What was that?

@Remy Lebeau Thanks for the answers. Much appreciated. We didn't write any codes for any TidTCPServer event handlers. The TransportServer is a TkbmMWTCPIPIndyServerTransport object, it uses TIdTCPServer internally as its Socket instance. What we did was that in OnServiceStartEvent, calling TransportServer.Listen (which calls TidTCPServer.Active := True), and in OnServiceStopEvent, calling TransportServer.Close (which calls TidTCPServer.Active := False), kbmMW handles everything else underneath (dealing with client side requests/server side responses). As for TerminateWaitTime property default to 5 seconds, we never set or change it by any chance, I thought Windows service timeout was set way longer (at least 30 seconds, we tested 90 seconds in the past) than TerminateWaitTime. The hard part was that we can't reproduce on our development machines. Only some of our customers who were heavily using the servers were having the issue. We don't know how to debug at this point and where we should look at from.

Yes. you can as long as fbclient.dll is the right one.

Could anyone help what the warning was about, Codes was fine in Delphi2007, but not in Delphi 10.4.1: ServiceMethod: TServiceMethod; which is a type of function (Sender: TObject, ...): variant of object;

Figured it out, the type should be a type of function, not object function.

Appreciated!

Hi, For the last couple of days I tried figure out the issue about Canvas.Polygon wasn't working properly. Here is my routine: procedure DrawTriangle(ACanvas: TCanvas; AColor: TColor; ARect: TRect); begin ACanvas.Brush.Style := bsSolid; ACanvas.Brush.Color := ColorToRGB(clRed); //ColorToRGB(AColor); ACanvas.Pen.Color := ColorToRGB(clRed); //ColorToRGB(AColor); //ACanvas.Pen.Mode := pmCopy; ACanvas.Polygon([Point(ARect.Right - 1, ARect.Bottom - 10), Point(ARect.Right - 1, ARect.Bottom - 1), Point(ARect.Right - 10, ARect.Bottom - 1)]); end; if I passed clRed as one of the Color parameter on the red background, it drawed a white triangle, as you see from the below screenshot,. It was only painted right at the most right column. Even I hard coded to set color to clRed, it still drawed a white triangle. I just can't figure out what I was doing wrong.

Solved the issue, but I don't understand the reason why, I had like: SaveIndex := SaveDC(Canvas.Handle); try IntersectClipRect(Canvas.Handle, .....); PaintRows(Canvas, ...); finally RestoreDC(Canvas.Handle, SaveIndex); end; The codes in procedure PaintRows: SaveIndex2 := SaveDC(ACanvas.Handle); try IntersectClipRect(ACanvas.Handle, .....); ..... PaintCells(ACanvas, ...); ...... finally RestoreDC(ACanvas.Handle, SaveIndex2); end; By removing the SaveDC/RestoreDC from procedure PaintRows, it solves, but Why? can't nest call SaveDC/RestoreDC??

Tried reversing the order of pen and brush assignments, doesn't work either.

@Anders Melander tried yours but still the same issue: procedure DrawTriangle(ACanvas: TCanvas; AColor: TColor; ARect: TRect); var SaveIndex: Integer; begin ACanvas.Lock; try SaveIndex := SaveDC(ACanvas.Handle); try ACanvas.Brush.Style := bsSolid; ACanvas.Brush.Color := clBlack; ACanvas.Pen.Color := clBlack; ACanvas.Polygon([Point(ARect.Right - 1, ARect.Bottom - 10), Point(ARect.Right - 1, ARect.Bottom - 1), Point(ARect.Right - 10, ARect.Bottom - 1)]); finally RestoreDC(ACanvas.Handle, SaveIndex); end; finally ACanvas.Unlock; end; end;

Tried without, it doesn't work either.

if I use clBlack instead:

I created a new post for my delphi ide editor themes, you may download the files from there:

Some one is asking for my themes, so I thought its better to create a new post to benefit any one who like them, I called them "Nature" themes, one Nature original theme and one Nature Warm theme, you may use Delphi IDE theme editor (https://github.com/RRUZ/delphi-ide-theme-editor) to apply them: Please click Like if you enjoy it. Nature warm (based on my Nature original theme): File: c0d3r-YW-Nature-warm.theme.xml

Nature: The brick red represents: Flowers, The green: Forest, the orange/yellow: Moon/Sun, the cream white: Clouds, the dark blue background: Deep ocean, the light green (blueish, used for comments) : Rivers. the brown white space: earth. the Sky blue brace pair highlight: The Sky. The red error lines: Fire. File: c0d3r-YW-Nature.theme.xml

Just realized that the compiler error counts were always offset by 1, so where is that extra one? Are the EMBRAS... guys able to count their fingers? if not, I can teach them.