[cosmic-users] WG: Cannot export IDL Files

[Pommrenke, Hendrik]

CoSMIC VERSION: 0.8.3 and last nightly build

HOST MACHINE and OPERATING SYSTEM: Windows XP 32-bit
TOOL/AREA/CLASS/EXAMPLE AFFECTED: IDL Export
DOES THE PROBLEM AFFECT:
 COMPILATION?
 LINKING?
 EXECUTION? yes
 OTHER (please specify)?
SYNOPSIS: Cannot export IDL Files
DESCRIPTION:

I have some idl files with my interfaces and components, from which I generate an xml file, which I import to CoSMIC in turn. When I try to export that model just imported using the "IDL export" button, I get a popup message from the IDL File Generator, saying "Object handle is null". When I confirm this message, I get another message from MgaUtil saying "Component error (0xfffffff): Object was not found". 

By the way, wouldn't it be handy to install some web-based bug tracking system for CoSMIC. That would make it easier to keep track of the status.

Cheers,
Hendrik


> -----Ursprüngliche Nachricht-----
> Von: Pommrenke, Hendrik
> Gesendet: Donnerstag, 13. Januar 2011 10:18
> An: James H. Hill
> Betreff: AW: [cosmic-users] Exported IDL files lack "#include" statements
> 
> Hi James,
> 
> I installed the nightly build, but I couldn't load my model generated with
> version 0.8.2. In the CoSMIC installation folder, the migration script
> from 0.8.2 to a higher version is missing, so I tried to load the xml I
> had generated with idl_to_picml of CoSMIC 0.8.2. But CoSMIC failed to open
> that file due to a paradigm inconsistency. Consequently, I generated the
> xml from my idls with the idl_to_picml from the nightly build, but it
> won't open either (same error messages:
> 
> Could not locate paradigm PICML
> Version ID: {0036...}
> Do you want to upgrade?
> Version ID: {6398...}
> 
> When I press okay, I get a message "Could not open paradigm PICML
> Version ID: {6398...}", and the next popup message says "The paradigm is
> invalid".
> 
> One idea would be to go back to CoSMIC 0.8.3. Is the #include problem
> solved there? And in general, is it safe to combine different versions (in
> our special case, CoSMIC 0.8.3 with CIAO 0.8.2?).
> 
> Cheers,
> Hendrik
> 
> 
> Looks like CoSMIC has forgotten
> > -----Ursprüngliche Nachricht-----
> > Von: James H. Hill [mailto:hillj at dre.vanderbilt.edu]
> > Gesendet: Mittwoch, 12. Januar 2011 18:59
> > An: Pommrenke, Hendrik
> > Cc: cosmic-users at list.isis.vanderbilt.edu
> > Betreff: Re: [cosmic-users] Exported IDL files lack "#include"
> statements
> >
> > Hi Hendrik,
> >
> > Thank you for using the PROBLEM-REPORT-FORM.
> >
> > On Jan 12, 2011, at 12:19 PM, Pommrenke, Hendrik wrote:
> >
> > > CoSMIC VERSION: 0.8.2
> > >
> > >     HOST MACHINE and OPERATING SYSTEM:
> > >       Windows XP 32-bit
> > >
> > >     TOOL/AREA/CLASS/EXAMPLE AFFECTED:
> > >       IDL Export
> > >
> > >     DOES THE PROBLEM AFFECT:
> > >         COMPILATION?
> > >         LINKING?
> > >         EXECUTION? Yes
> > >         OTHER (please specify)?
> > >
> > >     SYNOPSIS:
> > >       Exported IDL files lack "#include" statements
> > >
> > >     DESCRIPTION:
> > >
> > > Hello everybody,
> > >
> > > when I try to export the interfaces from my model using the "IDL"
> > > button, the resulting IDL files lack the necessary preprocessor
> > > directives to #include the used IDLs. Only "components.idl" is
> > > #included in all my IDL files. Some older version of the Stock
> > > Quoter tutorial contains a hint that filerefs in the
> > > "InterfaceDefinitions" folder correspond to #includes. So I tried to
> > > solve the problem by copying the top-level item under "Interface
> > > Definitions" whose corresponding IDL file I wanted to include, and
> > > pasting it as a reference into the top-level item where I want to
> > > include it. Thereby I generated a fileref pointing at the right
> > > file, but still no #includes after IDL export. As the fileref to
> > > #include connection stuff is no more mentioned in the latest
> > > tutorial version, I guess the behaviour has been modified in that
> > > aspect. What's the trick here?
> >
> > There is no trick. ;-)
> >
> > This problem has been resolved and should be fixed in the nightly
> > build available on the website. Please let me know if this does not
> > solve your problem. Sorry for any inconvenience.
> >
> > Thanks,
> >
> > James
> >
> > >
> > > Cheers,
> > > Hendrik
> > >
> > >
> >
> **************************************************************************
> > *****
> > > This e-mail message is intended only for the addresse(s) and contains
> > > information which may be confidential. If you are not the intended
> > > recipient please do not read, save, forward, disclose or copy the
> > > contents
> > > of this e-mail. If this e-mail has been sent to you in error, please
> > > delete this
> > > e-mail and any copies or links to this e-mail completely and
> > > immediately
> > > from your system. We also like to inform you that communication via
> > > e-mail
> > > over the Internet is insecure because third parties may have the
> > > possibility
> > > to access and manipulate e-mails.
> > >
> > > Any views expressed in this message are those of the individual
> > > sender,
> > > except where the sender specifically states them to be the views of
> > > The Swatch Group Ltd.
> > >
> >
> **************************************************************************
> > ***** _______________________________________________
> > > cosmic-users mailing list
> > > cosmic-users at list.isis.vanderbilt.edu
> > > http://list.isis.vanderbilt.edu/mailman/listinfo/cosmic-users

*******************************************************************************
This e-mail message is intended only for the addresse(s) and contains
information which may be confidential. If you are not the intended
recipient please do not read, save, forward, disclose or copy the contents
of this e-mail. If this e-mail has been sent to you in error, please delete this 
e-mail and any copies or links to this e-mail completely and immediately
from your system. We also like to inform you that communication via e-mail
over the Internet is insecure because third parties may have the possibility
to access and manipulate e-mails.

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
The Swatch Group Ltd.
*******************************************************************************