Delphi newby...
I have realised (too late) that Delphi does not support circular references between uses clauses.
I have two forms that communicate with each other, check values and update values between each others' forms.
In C++ I would use a base pointer to pass a reference to the other form and call the peer forms method, quite a simple matter.
In Delphi, I can't seem to do that. The base pointer produces an error and seems to need to explicitly know the type of the object. I can't use a 'class reference' the example 'class reference' code in help doesn't compile either. I can't use a generic form pointer. When I cast it up to the specific form object, it complains it doesn't know about the method I am calling.
I can't move the uses clauses out of the respective 'interface' &/or implementation' sections. They need to know about each other. I have read somewhere that 'circular references limitation' is a 'curse', carried over to Delphi.Net, that Delphi is still unable to fix or unwilling. As it is, a large part of the 'new' functionality of this application CANNOT BE IMPLEMENTED due to this restriction. This seems to seriously limit even the basic object oriented capabilities of Delphi.
Any info or comments this would be welcome.
I have realised (too late) that Delphi does not support circular references between uses clauses.
I have two forms that communicate with each other, check values and update values between each others' forms.
In C++ I would use a base pointer to pass a reference to the other form and call the peer forms method, quite a simple matter.
In Delphi, I can't seem to do that. The base pointer produces an error and seems to need to explicitly know the type of the object. I can't use a 'class reference' the example 'class reference' code in help doesn't compile either. I can't use a generic form pointer. When I cast it up to the specific form object, it complains it doesn't know about the method I am calling.
I can't move the uses clauses out of the respective 'interface' &/or implementation' sections. They need to know about each other. I have read somewhere that 'circular references limitation' is a 'curse', carried over to Delphi.Net, that Delphi is still unable to fix or unwilling. As it is, a large part of the 'new' functionality of this application CANNOT BE IMPLEMENTED due to this restriction. This seems to seriously limit even the basic object oriented capabilities of Delphi.
Any info or comments this would be welcome.