Dear All,
found kind a funny mistake in 2015 while importing another file.
The Logs button at the results list is working and can turn Logs on and off - but the Logs button in the right lower corner is off focus and not doing anything. Shouldn't that be 2 Buttons for one coding - seems not.
Have a look at the screen shot attached.
Regards,
Jay
Hi Jay,
I had a quick look and it works for me. It looks like in your case it's not 'active' for some reason, while on my machine i can click it and it works. see attached image.
Hanno
working fine..
1. close the study and re-open.
2. abort the study and re-run the same.
Hope it helps
Many thanks to all responders,
wasn't ment as an issue I wouldn't come along with - my interest was more on a coder basis.
Was wondering how one code for 2 buttons works on first while the second doesn't.
Or are there two different code lines one for each button to open/close Log file.
Regards,
Jay
Haven't been able to reproduce it. I tried to open a report also, as in your picture I can see one on your picture) but still no success.
If you find out a way to reproduce, please let us know.
Function to open the log is most likely the same in the code.
But here, we speak about availibility of a button who call that function. That is different, and as the log button is not attached to the same window (one is the graphic, one is the study management window), it can have different behavior(even if it shouldn't)
Dear Yannick,
It is not a report - what you see is the DesignLink import log window - and I think this depends.
BUT I will find a reproducible way and tell you - not a problem.
Regards,
Jay
Dear All,
Did it again! Reproducible when you do the following:
1. run a (long enough running) 3D Fill - after start you can turn logs on/off by those two buttons.
2. Import another catia V5 catpart file - use direct import Design Link - run
3. switch back to the running 3D Fill - button (graphic) lower right corner not active anymore and therefore not clickable - checkbox still works.
Regards,
Jay
Reproduced it too, and will log it in our bug tracking database.
Not that we are not developing anymore the legacy AMDL (the way you use it). So that it is not a common workflow.
Why you don't use direct import ? It offers much more possibilities.
Dear Yannick,
i used direct import: (for *.catpart)
but it is ok for me - figured out 2 bugs in under one week. (one high and one low)
2nd time: let's call it a day.
Many thanks to all!
Regards,
Jay
PS: prepare for my special sink marks file.