I see. I recall now having read in the User Guide about the need of
having an instance of a control before creating new controls of that
type. But this approach does work with user created objects. The
problem is then only with RealBasic controls. I suppose your program
does not have the object definition?
A possibility, then, would be create an user object with Canvas as
parent?
Juan Salvatierra
El 20/05/2006, a las 19:41, CV escribió:
dim o as new canvas
Typically, the compiler will let you do this but will not return o as
a functional canvas with a graphics object. When o.graphics.textfont =
"system" is attempted a nil object exception is raised.
The approach is to have an instance of canvas available in a "control
array", say Canvas1 with index = 0, and clone it like this:
dim o as canvas = new Canvas1
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>