这看起来是完全有效和正确的<>只有。 财产
published property FileName : String read FFileName;
如果你增加公共财产,因此在经营期间只能确定:
public property RuntimeFilename: string read FFileName write FFilename;
//note that two properties, one published and one public point to the same field.
However if you want to hack it and get rid of the exception in Design-time
change it to:
//Only writable during runtime.
private
procedure SetFileName(Value: string);
published
property FileName: string read FFileName write SetFileName;
....
procedure TMyClass.SetFileName(Value: string);
begin
if csDesigning in Componentstate then {do nothing}
else FFileName:= Value;
end;
www.un.org/Depts/DGACM/index_spanish.htm 我认为也可以做些什么。
Disconnect between designtime and runtime code
In order to change the runtime behaviour of the code you need only change the source code and remove the write ... part of the property.
This will not effect the design-time code though, for that you need to reinstall the component.
If you change the source code of a registered component and you keep the changes within the private, protected and/or public sections of the component you are usually OK.
但是,如果您修改了一部分内容的<代码>公布的<>>>,并且你不会再重复这一组成部分,你在开始时会有不正常的行为。
这是因为在设计时间上,你仍在使用该构成部分的老版/译本。 该版本的没有write/code>部分被删除<>/strong>,并允许您修改其背后示意图。
Come runtime the init-code will read the form resource 1) and spots a value to be written to FFilename. However the procedure SetFilename is no longer available and therefore a access violation occurs during program startup.
1 (现存放在您的的散射资源内的数据)。
