IBL points file crashes Wildfire II 1

[treddie]

Howdie.
I have a little vb6 program that builds IBL points files for me so that I can import these into ProE as Datum curves. It works great (simple thing really), but I have one file that keeps crashing ProE to the desktop. I have gone through the file and selectively removed blocks of points to try to isolate where in the file the suspect point is, but each block I test has been successful (not crashed ProE). In this manner, I have tested all of the point sets in the file to find out whether there is a problem in my code, or in ProE. There are 353 points total in the file, with 3 sets containing 103 points each. It is these 3 large sets that I selectively removed points and tested the results. Is there a known bug in ProE concerning IBL files in general, or is there a limit to the amount of points that can be in an IBL file? Again, all of the data works when I remove points from the three long sets, I just can't get the WHOLE file to work with ProE all at once. I COULD break the file up into 3 separate files (and this works), but that's a bit of a drag, if this problem is fairly frequent.
Thanks everyone,
treddie

 

[cadcamguy]

ibl can be a little weird... I have done the same as you with vb6.. which by the way rocks with ProE I have a least 20 different vb programs I have working with vb&pro.

I don't know how we can exchange info or source code except maybe over at mcadcentral.... so if you post a message over there.. I will keep a eye out and we could go from there.

 

[cadcamguy]

otherwise .. we may end up turning this into a VB6 code thread

 

[treddie]

Sorry cadcamguy.
I've been on vacation and won't be back until around New Year's.
Until then, have a great New Year's Day and hope you had a great Christmas.
treddie

 

[cadcamguy]

Treddie,

No problem.. enjoy the vacation and Happy Holidays to you and your family.

 

[cadcamguy]

There are 353 points total in the file, with 3 sets containing 103 points each. It is these 3 large sets that I selectively removed points and tested the results. Is there a known bug in ProE concerning IBL files in general, or is there a limit to the amount of points that can be in an IBL file?

hmmm... 200 curves ..181 points per curve... 36,200 points...

I got source code for ya .. but you will have to do the mcadcentral thing so I can private message you

 

[treddie]

Hi cadcamguy.
I hope your holidays were exquisite.
Sorry it took so long to get back to you.
How do I contact you over at mcadcentral?
treddie

 

[cadcamguy]

just post something about ibl files and then I can pm you there..

 

[treddie]

Will do.

 

[treddie]

I have posted the same post over in mcadcentral/data translation forum.

See you over there.

treddie

 

[treddie]

I finally figured out the problem. I knew previously that file pathnames that are too long can crash W2 to the desktop, but I thought I tested that possibility for this file. Turns out I didn't. I went back and moved the IBL file to a location with a very short pathname and everything works fine now. The issue does not appear to be too many subdirectories, but the overall amount of characters in the path. It so happens, that this particular file had a long name. Add that to the particularly long PATH to the file, and W2 had a heart attack.

Does anyone know of a good reference on the IBL file format? I have had about zero luck trying to find one. In fact, the reason I was able to build my simple files at all was because I found a sample on the web, but it did not include commands or statements at all, beyond the standard "Open Arclength" and "Begin" headers.

Thanks again!

treddie

 

[cadcamguy]

there is very little info .. I forgot where I found what I did but it was pretty limited anyway..

the ;
Closed Index Arclength

Begin section ! 1
Begin curve ! 1

list of points for curve 1
Begin curve ! 2


list of 2nd points

Begin curve ! 3

again over and over till you have all your sets


nothing needed to close out file.. tho the example I found< I think had something ... it works with nothing

 

[cadcamguy]

I went back and moved the IBL file to a location with a very short pathname and everything works fine now. The issue does not appear to be too many subdirectories, but the overall amount of characters in the path...

dim a string for your filename in general declarations

say;

dim fname as string


add a drivelistbox, a dirlistbox, and a filelistbox,

them up so it sets your subdir.. using the change property

then to get around the long file name issue your fname can be... you can even get alittle exotic and have it follow proes working dir with chdir

fname =dir1.path & "\" & file1.filename before you process
command1._click that allows for some longer file names

 

[treddie]

That's basically what I do. The problem is that once I build a successful IBL file in vb6, ProE is the monster that can't handle the long pathnames and it crashes.Incidentally, I noticed a slight difference in your IBL format from mine. Mine starts out:
Open Arclength

Begin section ! 1
Begin curve ! 0
Points list

Begin section ! 2
Begin curve ! 1
Points list

Begin section ! 3
Begin curve ! 2
Points list

and so on...
'------------------------------------
Yours is:
Closed Index Arclength

Begin section ! 1
Begin curve ! 1
Points list

Begin curve ! 2
Points list


Begin curve ! 3
Points list

and so on...

Am I correct in assuming that "Open" and "Close" refer to open or closed curves? But what is "Index"? Also, was never clear on the "Begin Section" deal and I found I needed to use it as shown to get the correct results.

Was talking to wsylvester over at mcadcentral and he had this sample:

i set the step to 45 ;

Closed Index Arclength

Begin section ! 1
Begin curve ! 1
1 ; 100. 0.0 &nb sp; 0.0
46 &nbs p; 70.7107 35.3553 0.0
91 &nbs p; 0.0 &nb sp; 50. &nb sp; 0.0
136 &nb sp; -70.7107 35.3553 0.0
181 &nb sp; -100. 0.0 &nb sp; 0.0

Begin curve ! 2
1 ; 100. 0.0 &nb sp; 10.
46 &nbs p; 70.7107 35.3553 10.
91 &nbs p; 0.0 &nb sp; 50. &nb sp; 10.
136 &nb sp; -70.7107 35.3553 10.
181 &nb sp; -100. 0.0 &nb sp; 10.

SOMEWHERE, there has to be an IBL format reference.