Behaviour of ProDrawingDtlsyminstsCollect() API for different date codes

[skashyap]

Hi All,

I am facing issue with ProDrawingDtlsyminstsCollect() API.

I am creating custom BOM  balloons, and collecting these balloons with ProDrawingDtlsyminstsCollect() API.

With M100 date code it is able to collect, but with M150 its giving an error PRO_TK_NOT_FOUND.

Is there any other way to collect BOM balloons?

Thanks in advance!

Regards,

Y S Srikanth Kashyap

[FV]

Try ProDrawingDtlsyminstVisit(...). HH.

[skashyap]

Hello,

I tried with API too. It is also giving PRO_TK_NOT_FOUND.

Is there any other workaround for this issue?
Regards,

Y S Srikanth Kashyap

[FV]

Hard to tell based on available information. What version of Pro/E are you using in the first place? Did you contact tech support? Did you try to run Collect or Visit function from the code which have an interactive selection of the detail entities. What are your debugger settings? Is code compiled as C or C++?

[skashyap]

I am using Creo 2.0 M150. I did contact tech support. They were tell telling that custom BOM balloons are made private for M150 build code.

Code is in C++.

Is there any other way to collect BOM balloons? Maybe by VB API or anything?

[FV]

Hi all,

ProDrawingDtlsyminstVisit works in Creo 3.0 Parametric M040 with custom balloon symbols created with \INDEX\ variable text with default value asm.mbr.SOME_PARAM. ProDtlsyminstDataGet is also working within visit-action and filter-action functions. The working code for the active drawing with the current sheet #1:

err = ProDrawingSheetsCount( drawing, &n_sheets);

for( int sht_id = 1; sht_id <= n_sheets; sht_id++){

err = ProDrawingDtlsyminstVisit( drawing, sht_id,

(ProDtlitemVisitAction) _va , (ProDtlitemFilterAction) _fa,

(ProAppData) NULL  );

}

Feliks.

[skashyap]

Hi Feliks,

I agree that it will work in Creo 3.0 M040.

Also it works in Creo 2.0 all build codes except M150.

It is a vague behaviour of API.

I consulted technical support. They said that it has been made private for this particular version. i.e, M150

Regards,

Y S Srikanth Kashyap

[sthangaraj]

It does not works in Creo 2.0 M120 also and works on M100, M180