🚀 go-pugleaf

Hello Christian,

>A long time ago Gerrit Beuze posted the following message, but no one ever
> replied.  Well, I have the exact same issue, except with D2006.  So I'm
> wondering how this turned out or what the work around is.

Situation is still the same. No real work arounds.
Work around = make sure you have your form visible in *all* desktop files
including project desktops. Even if it is just hidden in a tab somewhere.
You might need to delete (temp rename?) exsiting ide + project desktops
and restart from scratch.

Gerrit Beuze
ModelMaker Tools

"Gerrit Beuze" <gerrit[at][-nospam]modelmakertools[dot]com> wrote in message 
news:47cf9449@newsgroups.borland.com...
> Hello Christian,
>
>>A long time ago Gerrit Beuze posted the following message, but no one ever
>> replied.  Well, I have the exact same issue, except with D2006.  So I'm
>> wondering how this turned out or what the work around is.
>
> Situation is still the same. No real work arounds.
> Work around = make sure you have your form visible in *all* desktop files
> including project desktops. Even if it is just hidden in a tab somewhere.
> You might need to delete (temp rename?) exsiting ide + project desktops
> and restart from scratch.
>
> Gerrit Beuze
> ModelMaker Tools
>


Thanks for getting back so quickly.

Sorry to hear there's no real fix.  It did occur to me, however, to erase 
the desktop files and start over with those.  My only fear is that if/when I 
distribute this, what do I tell my users?  Do I also run some code that 
alters all of their desktop files?

Again, thanks for the help.  Also, keep up the good work on ModelMaker.  I'm 
not sure what I'd do without it.

-- 
Christian Wilkerson
Home made country music
@ http://www.myspace.com/christianwilkersonmusic

And now with Blog!

>>>A long time ago Gerrit Beuze posted the following message, but no one 
>>>ever
>>> replied.  Well, I have the exact same issue, except with D2006.  So I'm
>>> wondering how this turned out or what the work around is.
>>
>> Situation is still the same. No real work arounds.
>> Work around = make sure you have your form visible in *all* desktop files
>> including project desktops. Even if it is just hidden in a tab somewhere.
>> You might need to delete (temp rename?) exsiting ide + project desktops
>> and restart from scratch.
>>
>> Gerrit Beuze
>> ModelMaker Tools
>>
>
>
> Thanks for getting back so quickly.
>
> Sorry to hear there's no real fix.  It did occur to me, however, to erase 
> the desktop files and start over with those.  My only fear is that if/when 
> I distribute this, what do I tell my users?  Do I also run some code that 
> alters all of their desktop files?
>
> Again, thanks for the help.  Also, keep up the good work on ModelMaker. 
> I'm not sure what I'd do without it.
>


Well, I think I've figured it out.  Once I removed FormCreate and 
FormDestroy events everything seems to work fine.  When I say removed, I 
mean completely commented or deleted from the source.

I'm reasonably confident that this is the case because when I re-inserted 
them, the problems came back.  I was also surprised that just having them 
there (not hooked up to the dfm), caused issues.  Perhaps somebody with more 
knowledge can shed light on this.

Anyhow, I'm very happy to have this figured out, and Gerrit, thanks again 
for your help.

-- 
Christian Wilkerson
Home made country music
@ http://www.myspace.com/christianwilkersonmusic

And now with Blog!

> Well, I think I've figured it out.  Once I removed FormCreate and FormDestroy events everything seems to work fine.  When I say 
> removed, I mean completely commented or deleted from the source.
> I'm reasonably confident that this is the case because when I re-inserted them, the problems came back.  I was also surprised that 
> just having them there (not hooked up to the dfm), caused issues.

They are published methods and the RTTI TObject.MethodName will point to
your methods, *even* if they are not hooked in the designer.
This is interesting: perhaps it also works if you call "inherited" in your methods?


> Anyhow, I'm very happy to have this figured out, and Gerrit, thanks again for your help.

And thank you for getting back.
This could lead to a general solution for the problem.

Gerrit Beuze
ModelMaker Tools 

> Well, I think I've figured it out.  Once I removed FormCreate and FormDestroy events everything seems to work fine.  When I say 
> removed, I mean completely commented or deleted from the source.

Just checked the source:
The Code Explorer - which works OK - has an FormCreate and FormDestroy and *does* call "inherited;"
as the last thing in the OnCreate eventhandler.
The Source Indexer - which does *not* work OK, does *not* call inherited,

I think you've got it figured out!

Gerrit Beuze
ModelMaker Tools 

"Gerrit Beuze" <gerrit[at][-nospam]modelmakertools[dot]com> wrote in message 
news:47d18210@newsgroups.borland.com...
>> Well, I think I've figured it out.  Once I removed FormCreate and 
>> FormDestroy events everything seems to work fine.  When I say removed, I 
>> mean completely commented or deleted from the source.
>
> Just checked the source:
> The Code Explorer - which works OK - has an FormCreate and FormDestroy and 
> *does* call "inherited;"
> as the last thing in the OnCreate eventhandler.
> The Source Indexer - which does *not* work OK, does *not* call inherited,
>
> I think you've got it figured out!
>
> Gerrit Beuze
> ModelMaker Tools

Good to know.

Wow, I feel a little like a cold case detective.

BTW and OT, Greg Stevenson says he'll be done with the help project this 
weekend (although he says you've heard that before).

-- 
Christian Wilkerson
Home made country music
@ http://www.myspace.com/christianwilkersonmusic

And now with Blog!