Error when closing the editor form with cursor inside a table cell

General TRichView support forum. Please post your questions here
Post Reply
edwinyzh
Posts: 104
Joined: Sun Jun 05, 2022 2:22 pm

Error when closing the editor form with cursor inside a table cell

Post by edwinyzh »

When destroying a form with a TRichViewEdit which has a table and has a cell focused, the following error will happen.

My workaround now is to call `DestroyInplace` before in the form's OnClose event, but I'd still report the issue.

Call stack:

Code: Select all

exception class    : EAccessViolation
exception message  : Access violation at address 00DD3A54 in module 'program1.exe'. Read of address 00000040.

main thread ($3b8):
00dd3a54 +060 program1.exe CRVData         2370   +6 TCustomRVData.GetOffsAfterItem
00e60f52 +006 program1.exe RichView        2562   +0 TCustomRichView.GetOffsAfterItem
00e50603 +037 program1.exe RVLinear         968   +6 RVGetTextLength
00e66080 +034 program1.exe RichView        6365   +9 TCustomRichView.WMGetTextLength
005c8c5d +2bd program1.exe Vcl.Controls    7224  +91 TControl.WndProc
005cd719 +5c5 program1.exe Vcl.Controls   10039 +153 TWinControl.WndProc
00e67000 +078 program1.exe RichView        6944  +17 TCustomRichView.WndProc
00c951b1 +145 program1.exe RVTInplace       809  +43 TRVTableInplaceEdit.WndProc
005c8898 +024 program1.exe Vcl.Controls    7002  +10 TControl.Perform
005c72bd +009 program1.exe Vcl.Controls    6050   +0 TControl.GetTextLen
005cf533 +013 program1.exe Vcl.Controls   11308   +6 TWinControl.WMDestroy
00df56e8 +014 program1.exe RVScroll         702   +2 TRVScroller.WMDestroy
00e62cc5 +011 program1.exe RichView        4067   +2 TCustomRichView.WMDestroy
00d5b7cc +038 program1.exe RVEdit          1447   +7 TCustomRichViewEdit.WMDestroy
005c8c5d +2bd program1.exe Vcl.Controls    7224  +91 TControl.WndProc
005cd719 +5c5 program1.exe Vcl.Controls   10039 +153 TWinControl.WndProc
00e67000 +078 program1.exe RichView        6944  +17 TCustomRichView.WndProc
00c951b1 +145 program1.exe RVTInplace       809  +43 TRVTableInplaceEdit.WndProc
005ccd5c +02c program1.exe Vcl.Controls    9751   +3 TWinControl.MainWndProc
0054af80 +014 program1.exe System.Classes 16860   +8 StdWndProc
77bb0107 +02b ntdll.dll                                 KiUserCallbackDispatcher
76f29a75 +00e USER32.dll                                DestroyWindow
005cc708 +040 program1.exe Vcl.Controls    9511   +5 TWinControl.DestroyWindowHandle
006c75ef +04b program1.exe Vcl.Forms       5644   +8 TCustomForm.DestroyWindowHandle
006c3f4b +073 program1.exe Vcl.Forms       3715  +25 TCustomForm.Destroy
Sergey Tkachenko
Site Admin
Posts: 17557
Joined: Sat Aug 27, 2005 10:28 am
Contact:

Re: Error when closing the editor form with cursor inside a table cell

Post by Sergey Tkachenko »

Do you use the newest version of TRichView?
Do you process some events of TRichViewEdit that may be called when closing/destroying?
edwinyzh
Posts: 104
Joined: Sun Jun 05, 2022 2:22 pm

Re: Error when closing the editor form with cursor inside a table cell

Post by edwinyzh »

Sergey Tkachenko wrote: Tue Jun 21, 2022 9:11 am Do you use the newest version of TRichView?
I use the latest version downloaded on 2022-June-05.
Sergey Tkachenko wrote: Tue Jun 21, 2022 9:11 am Do you process some events of TRichViewEdit that may be called when closing/destroying?
I just double checked it, I don't think so.
Sergey Tkachenko
Site Admin
Posts: 17557
Joined: Sat Aug 27, 2005 10:28 am
Contact:

Re: Error when closing the editor form with cursor inside a table cell

Post by Sergey Tkachenko »

Can you create a sample project reproducing this problem? Because I cannot reproduce it on TRichView demo projects.
edwinyzh
Posts: 104
Joined: Sun Jun 05, 2022 2:22 pm

Re: Error when closing the editor form with cursor inside a table cell

Post by edwinyzh »

Sergey Tkachenko wrote: Wed Jun 22, 2022 9:42 am Can you create a sample project reproducing this problem? Because I cannot reproduce it on TRichView demo projects.
Hi Sergey,

Maybe in the future, or I'll definitely post any possible new findings regarding this issue. anyways, I've a workaround ;)
Post Reply