Sean,

I was wondering of you have been able to get a windows version of proe-brl for 
pro-engineer to work.

We are having to migrate to the 64bit version of Pro-E (WinXP 64) and need to 
get the convertor to work with this version.   It looks like, from brlcad.org 
page that you were able to get a 64bit version of brlcad working.  So I was 
hoping for some advice on getting the convertor working in 64 bits.  We have 
not had luck in getting other 32bit plugins to work with the 64bit Pro/E so 
have not yet tried to use the exisiting 32 bit proe-brl plugin with 64 bit 
Pro/E.  We were hoping your developer mentioned below had gone down this path 
before.  Could we get contact info for him to consult about this?

Thanks,

Kathryn Cook
Senior Staff Mechanical Engineer - Lethality
Lockheed Martin Missiles and Fire Control - Dallas
M/S SP-68
P.O. Box 650003
Dallas, TX 75265-0003
Phone: 972-603-9095
Email: [email protected]




-----Original Message-----
From: [email protected] [mailto:[email protected]] 
Sent: Wednesday, July 30, 2008 4:35 AM
To: Cook, Kathy
Cc: [email protected]
Subject: Re: [brlcad-users] Proe-brl convertor loading error after compiling 
for Windows

Kathy,

That's great news!  Glad to hear you got it working.

On an entirely related coincidental note, one of our devs (Bob) has  
been working on getting the converter updated and working on our end  
too.  He ran into various issues with the biggest being  
incompatibilities between Microsoft's MSVC 2005 and the ProTk  
Wildfire libraries.  You were fortunately using 2003 so you avoided  
the issue.  When this is ready, it'll be certainly pointed out in our  
release notes.

As to your questions, the main one sounds like something has probably  
changed in the Pro/Tk API causing the behavior change.  Either that  
or a bug in Pro/E itself -- it's clearly bad behavior regardless.   
Unfortunately I don't have a quick bandaid to tell you.  What is the  
exact text it's telling you in the modal warning dialog?  We don't  
specifically create any modal dialogs on our end that I see.

So for that hang, no -- going to 7.12.2 shouldn't really change that.

Your message to brlcad-devel was rejected because you're not  
subscribed.  All of the mailing lists are configured that way to  
prevent spam.

Cheers!
Sean



On Jul 18, 2008, at 11:56 AM, Cook, Kathy wrote:

> Sean,
>
> I found my stupid error: I had not gotten the text folder for proe-brl
> into the protk_appls folder.  But the error was not very informative.
>
> But now it is loading into Wildfire 3.0.  Note that I am still on  
> 7.8.0.
> I tried a simple part to convert and chose Eliminate small features  
> and
> set the hole size to 7mm.  During the conversion, there is a dialog  
> box
> from the plugin that pops up warning about suppressed parts.  But
> clicking on the OK button does not work.  I could not close it with  
> the
> x in the corner either.  The main plugin dialog box showed the
> conversion was complete, but with that modal warning dialog box  
> still up
> I could not close that (or interact with Pro/E) either.  So I had  
> to use
> Task Manager to kill Pro/E.
>
> The converted part (via asc2g.exe) loaded into MGED and looks OK.
>
> Do you think going to 7.12.2 would help.  I know I need to do that
> anyway.
>
> P.S. I tried to reply to brlcad-devel but it was rejected.
>
> Thanks,
> Kathy
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Friday, July 18, 2008 12:47 AM
> To: Cook, Kathy
> Cc: [email protected];
> [email protected]
> Subject: Re: [brlcad-users] Proe-brl convertor loading error after
> compiling for Windows
>
>
> FYI, moving the discussion over to the brlcad-devel mailing list since
> it's more appropriate for this topic.
>
>
> Kathy,
>
> I did make a handful of changes to the proe-asc.c sources so that the
> plugin allows spaces in the part name mapping file and it'll create a
> different top-level if there is already a 'top' object being imported.
> Translation, those are some pretty trivial mods.  There haven't  
> been any
> changes that should affect the PRO_TK_GENERAL_ERROR that you're  
> getting.
> That is indeed a pretty useless error.
>
> One of our devs has been looking at getting the plugin working for  
> Pro/E
> on Windows just recently (this week) but we don't have an ETA.
>
> Any 7.12.2 libs should be compatible with other 7.12 sources you come
> across.  I don't know of there being any issues that would affect you
> with this compile.  You may also have an even easier time compiling  
> just
> the plugin using the BRL-CAD for Windows Runtime Libs (also on the
> sf.net project site downloads).  I don't know if it includes all  
> symbols
> you need, but it's worth a try.  Either way, compiling 7.12 for  
> Windows
> should be a whole lot easier than 7.8 was.
>
> Cheers!
> Sean
>
>
>
> On Jul 17, 2008, at 1:22 PM, Cook, Kathy wrote:
>
>> Over 2 years ago I was able (with much help from Sean Morrison) to
>> compile the proe-brl ProToolKit plugin for Wildfire 2.0.  The last
>> time I built it was using BRLCAD 7.8.0 source files for the plugin  
>> and
>
>> the Windows libs from BRLCAD for Windows.
>>
>> I now have to rebuild it for Wildfire 3.0 and after help from PTC
>> support on the required changes to the make file, I was able to
>> recompile (still using BRLCAD 7.8.0).  It compiled OK (using nmake
>> from the Visual Studio 2003 command prompt).  But when I try to load
>> with Pro/E I get the error message:
>>
>> Forgein process "proe-brl" failed to initialize: error
>> PRO_TK_GENERAL_ERROR failed to add proe-brl menu button.
>>
>> There is no other indication of what is wrong or where the error
>> occurred.
>>
>> I downloaded the latest source (7.12.4) and noticed that there have
>> been some changes to the proe-asc.c file and thought to try the new
>> version to see if that helps at all.  I noticed that the latest
>> Windows BRLCAD (which I will need the *.lib files from ) is
>> 7.12.2   Will these work together? Is there a 7.12.4 for Windows
>> coming soon?  Should I get the source for 7.12.2 instead?  I have not
>> checked if that one has the same changes to the proe-asc.c file.
>>
>> Any suggestions on how to proceed?  We no longer have an SGI  
>> available
>
>> to use the distibuted plugin
>>
>> Thanks,
>> Kathy Cook
>>
>> --------------------------------------------------------------------- 
>> -
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge Build the coolest Linux based applications with Moblin  
>> SDK &
>
>> win great prizes Grand prize is a trip for two to an Open Source  
>> event
>
>> anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> BRL-CAD Users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/brlcad-users
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> BRL-CAD Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/brlcad-users


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
BRL-CAD Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-users

Reply via email to