Double pins

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 29/08/2004 at 14:57, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   8.100
Platform:   Windows ; Mac ; Mac OSX ;
Language(s) :   C.O.F.F.E.E ;

---------
I have a problem with all my plug-ins.
After closing their window, when I call them a second time, I get double pins in the window.
This is a example of what I get:

http://www.ruimac.com/images/doublepins.gif

Why does this happen and how can I prevent it?
Thank you very much in advance.

Rui Batista

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 30/08/2004 at 23:38, xxxxxxxx wrote:

Come on!! It is very important that I sort this out. It never happened to anyone?
Please!! Pretty please...

Rui Batista

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 01/09/2004 at 14:35, xxxxxxxx wrote:

I can't believe this only happens to me. Come on!! Anyone?

Rui Mac

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/09/2004 at 01:09, xxxxxxxx wrote:

Perhaps you're the only one still using C.O.F.F.E.E....
I don't have 8.1 available for testing, but I couldn't confirm this with the AsyncBounce.cof on 8.503. Are there any differences between AsyncBounce and your plugin that could explain the error?

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/09/2004 at 01:20, xxxxxxxx wrote:

Quote: Originally posted by Mikael Sterner on 02 September 2004
>
> * * *
>
> Perhaps you're the only one still using C.O.F.F.E.E....
>
> * * *

Not really
I believe there are lots of people still using C.O.F.F.E.E.
Do you really believe that graphic designers, like myselft, will invest on a C++ compiler? What we need is that C.O.F.F.E.E. evolves a little more.

> Quote: _
>
> I don't have 8.1 available for testing, but I couldn't confirm this with the AsyncBounce.cof on 8.503. Are there any differences between AsyncBounce and your plugin that could explain the error?
>
> * * *
_

I don't have AsyncBounce here with me right now (I'm on my laptop) but, if I remember correctly, it created the dialog using direct C.O.F.F.E.E. statements. My plug-ins use resource files created with Resedit. Could it be the way I'm evoking the dialog?

Rui Batista

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/09/2004 at 01:58, xxxxxxxx wrote:

AsyncBounce can be downloaded from the download section of PluginCafe, in the 6.303 C.O.F.F.E.E. documentation package. Yes, perhaps it's the way the dialog is evoked. Please try evoking it like in AsyncBounce just to see if it makes any difference.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 02/09/2004 at 07:25, xxxxxxxx wrote:

They are not comparable. The asyncbounce.cof creates a layout, mine loads a resource

Rui Batista

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/09/2004 at 13:05, xxxxxxxx wrote:

Does the problem go away if you code the layout as a resource instead of creating the layout manually?

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/09/2004 at 15:53, xxxxxxxx wrote:

Nope. I never create the layout manually. I always use resources.

Rui Batista

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 21/09/2004 at 16:15, xxxxxxxx wrote:

Ok, fixed!! I found out the little bug.

Instead of:

CalcMenu::Execute(doc)  
{  
if(!bc) bc=new(BaseContainer);  
dialog = new(PluginDialog);  
dialog->SetContainer(bc);  
dialog->Open(TRUE,-1,-1);  
bc=dialog->GetContainer();  
return TRUE;  
}

I had:

  
CalcMenu::Execute(doc)  
{  
if(!bc) bc=new(BaseContainer);  
**var** dialog = new(PluginDialog);  
dialog- >SetContainer(bc);  
dialog->Open(TRUE,-1,-1);  
bc=dialog->GetContainer();  
return TRUE;  
}

Its odd what just three little characters can do

Rui Batista