TFDMoniFlatFileClientLink不定期地不跟踪到文件 [英] TFDMoniFlatFileClientLink irregularly does not trace to file
问题描述
我在表单上有一个TFDMoniFlatFileClientLink
,文件名设置为d:\temp\monitor.txt
,tracing = true,TFDConnection.Params.MonitorBy=mbFlatFile
.这有时可行,有时却无法跟踪任何内容.没有文件被创建.
I have a TFDMoniFlatFileClientLink
on a form, filename set to d:\temp\monitor.txt
, tracing=true, TFDConnection.Params.MonitorBy=mbFlatFile
. This sometimes works and sometimes does not trace anything. No file gets created.
在Win7 32位应用程序中经过测试,设计时间为TFDConnection
到FireBird或Oracle.德尔福东京10.2.1
Tested with Win7 32-bit app, with design time TFDConnection
to either FireBird or Oracle. Delphi Tokyo 10.2.1
这是怎么回事?
推荐答案
这是一个非常奇怪的错误:
This was a really weird bug:
事实证明,TFDMoniFlatFileClientLink
在删除并放回原位时会记住文件名,然后不会跟踪.
It turns out that the TFDMoniFlatFileClientLink
remembers the filename when removed and placed back, then does not trace.
要复制:
删除TFDMoniFlatFileClientLink
,可以选择保存项目,再次在窗体上放置TFDMoniFlatFileClientLink
,设置tracing = true.它已经神奇地记住了文件名d:\temp\monitor.txt
(在哪里?),然后要么不跟踪,要么跟踪到C:\Users\username\AppData\Local\Temp\traceX.txt
.
Remove the TFDMoniFlatFileClientLink
, optionally save the project, place a TFDMoniFlatFileClientLink
on the form again, set tracing=true. It has magically remembered filename d:\temp\monitor.txt
(where?), then either does not trace or traces to C:\Users\username\AppData\Local\Temp\traceX.txt
.
仅当您更改文件名时,它才能再次成功跟踪. *
TFDMoniRemoteFileClientLink
发生类似的奇怪事件,但通常不会为FDMonitor生成跟踪输出.我尚未调查发生这种情况的确切条件.
Similar weird things happen with TFDMoniRemoteFileClientLink
, it very often does not create trace output for FDMonitor to pick up. I have not investigated the exact conditions under which this happens.
在跟踪可能与以下问题有关的以下问题后,我在测试应用程序中发现了此问题: **
I found this in a test app after tracing the following issue, possibly related:**
设计时TFDConnection
在运行时填充其参数.我执行了TFDConnection.Params.Add('MonitorBy=mbFlatFile')
,但该应用程序未跟踪.我在运行时验证了MonitorByInitial=true
. Params.Add('MonitorBy=mbRemote')
也失败了.
在设计时将TFDMoniFlatFileClientLink
和TFDMoniRemoteClientLink
放置在数据模块上.
A design time TFDConnection
gets its parameters filled at run-time. I executed TFDConnection.Params.Add('MonitorBy=mbFlatFile')
but the app did not trace. I verified that MonitorByInitial=true
at run-time. Params.Add('MonitorBy=mbRemote')
also failed.
A TFDMoniFlatFileClientLink
and TFDMoniRemoteClientLink
were placed on the datamodule at design time.
在Embarcadero质量门户网站中的报告为 RSP-19554
Reported in Embarcadero Quality Portal under issue RSP-19554
*即使将其更改为相同的文件名.如果在运行时执行此操作,则必须在FileName分配周围设置Tracing=false/true
.
**毫米,不相关.报告为 RSP-19559
这篇关于TFDMoniFlatFileClientLink不定期地不跟踪到文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!