SimplifiedLogic / creoson

OpenSource Automation using JSON Transactions for PTC's CREO Parametric
http://www.creoson.com
MIT License
79 stars 23 forks source link

Warnings/Error pop-ups handling via code #109

Open nirav-98 opened 5 months ago

nirav-98 commented 5 months ago

If the method raise the warning, the warning pop up is created in the creo app, how can I handle that via creopyson? I don't get any warnings in the code execution, it's directly coming in the creo app. I need to read/access or know the warning that is being raised and handle it in code only.

adama2000 commented 5 months ago

There isn't a way for us to see warnings that pop up inside the Creo app. The only thing we can see is if the Creo API throws an error back to creoson/creopyson, and we can then return that to the caller.

Want kind of warning are you seeing?

On Mon, Mar 11, 2024 at 8:42 AM nirav-98 @.***> wrote:

If the method raise the warning, the warning pop up is created in the creo app, how can I handle that via creopyson? I don't get any warnings in the code execution, it's directly coming in the creo app. I need to read/access or know the warning that is being raised and handle it in code only.

— Reply to this email directly, view it on GitHub https://github.com/SimplifiedLogic/creoson/issues/109, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANPKPF7LSXCTQYMBNW5V7TYXWRENAVCNFSM6AAAAABEQHLOI2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TSMBUGA4TIMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

nirav-98 commented 5 months ago

There isn't a way for us to see warnings that pop up inside the Creo app. The only thing we can see is if the Creo API throws an error back to creoson/creopyson, and we can then return that to the caller. Want kind of warning are you seeing? On Mon, Mar 11, 2024 at 8:42 AM nirav-98 @.> wrote: If the method raise the warning, the warning pop up is created in the creo app, how can I handle that via creopyson? I don't get any warnings in the code execution, it's directly coming in the creo app. I need to read/access or know the warning that is being raised and handle it in code only. — Reply to this email directly, view it on GitHub <#109>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANPKPF7LSXCTQYMBNW5V7TYXWRENAVCNFSM6AAAAABEQHLOI2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TSMBUGA4TIMA . You are receiving this because you are subscribed to this thread.Message ID: @.>

I'm making a generic tool for reading creo metadata. So, test file set can be anything. Below is the pop-up I'm getting:(

image

And util I manually press Ok or X, it doesn't go away, the error/warning is raised in code after this manual intervention. I have tried changing the config of creo app, kept all the notification to "do not show", but this is still coming.

nirav-98 commented 5 months ago

So, without opening the file, can I know that file can be opened or not ? @adama2000

DieSwartKat commented 5 months ago

@nirav-98 Where is the metadata file located? Also what are you using the read the metadata file?

In cases like this I've run Autohotkey functions to get rid of warning messages as they appear.

nirav-98 commented 5 months ago

@nirav-98 Where is the metadata file located? Also what are you using the read the metadata file?

In cases like this I've run Autohotkey functions to get rid of warning messages as they appear.

Hi @DieSwartKat Thanks for the response. I download the files in a temp folder and then change my creo's working directory to that temp folder. I'm using creopyson's apis only to achieve all this.


c = creopyson.Client()
c.connect()

c.creo_cd($temp_dir)

asm_open = c.file_open('*.asm', display=False)
prt_open = c.file_open('*.prt', display=False)
drw_ope = c.file_open('*.drw', display=False)

asm_params = c.parameter_list(file_='*.asm')
prt_params = c.parameter_list(file_='*.prt')
drw_params = c.parameter_list(file_='*.drw')

Right now, I have added a custom time out to kill and restart creo when I'm not able to open it for let's say 90 seconds.