FR3 manual

Comments

• zinvob

  August 2004 edited 8:46AM

  Just read the programmer manual. Why don't you integrate the
  "CreateUniqueName" into the create of your band objects instead of having to call it whenever you create a new band.
• zinvob

  August 2004 edited 8:46AM

  and not just the bands, everything seems to need this one executed..
• AlexTZ

  August 2004 edited 8:46AM

  CreateUniqueName cannot be integrated into constructor.
• zinvob

  August 2004 edited August 2004

  Why not. Whenever create is executed, the first thing it does is to create the instance. And the instance can be reached with the self pointer. If you have other problems, use class procedure.
  
  I can't see your problem. Only the fact that you call CreateUniqueName whenever you create something within your framework. That is just duplicated work.
• zinvob

  August 2004 edited 8:46AM

  Just make it virtual, and call it as the last thing inside the contructor. Then override it from every object that want's different name adjustments.
• AlexTZ

  August 2004 edited 8:46AM

  I just can't due to some restrictions in the FR code. In some cases the object can't be named immediately after creation.
• zinvob

  August 2004 edited 8:46AM

  How about default parameters, would make the changes smaller:
  
  constructor Create(CreateName: boolean = true);
  
  And then you could change it to false where you don't want to create the name. Or you should change your need for no name at some places. The way it's done now, don't seem like a good solution to me. But as you know, I don't have the source, so...