tartufon80
Guest
Good morning, everyone!
Since we went from wildfire 3 to creo 2, I started having some problems regarding macros.
in particular I noticed that often the macro was "planting" and was not performed completely.
Inquiring I realized that opening the config.pro with the wordpad editor (write), a text character of the macro had been replaced by a square, as if it did not recognize that font (see attachment). opening instead the config.pro with the known block (notepad), everything seemed correct: it seemed, because the macro did not want to know to turn.
as the first "intervention" I thought, through wordpad, to remove the hulled character with the correct one. apparently everything ok, but after some time (hours, days, interval altogether random) the same problem is resumed in the text of other macros (also this random).
Since the problem has become frequent (I often use macros and I often add new ones) we have opened a call to ptc support (by sending our config.pro on their request).
after a different time they responded to us and I refer to you the "sentence":
"r&d says the config.pro in question contains many corruptions.are due to the wordpad that is unable to edit the utf-8 coding without corrupting the data. "I started using the notepad as editor, and "talk" that those problems have disappeared.
two considerations:
1 - in wf3 I used wordpad and never had such a problem
2 - the macros I had, apart from corruptions, work perfectly also in creo 2
Did any of you have any such problems?
Since we went from wildfire 3 to creo 2, I started having some problems regarding macros.
in particular I noticed that often the macro was "planting" and was not performed completely.
Inquiring I realized that opening the config.pro with the wordpad editor (write), a text character of the macro had been replaced by a square, as if it did not recognize that font (see attachment). opening instead the config.pro with the known block (notepad), everything seemed correct: it seemed, because the macro did not want to know to turn.
as the first "intervention" I thought, through wordpad, to remove the hulled character with the correct one. apparently everything ok, but after some time (hours, days, interval altogether random) the same problem is resumed in the text of other macros (also this random).
Since the problem has become frequent (I often use macros and I often add new ones) we have opened a call to ptc support (by sending our config.pro on their request).
after a different time they responded to us and I refer to you the "sentence":
"r&d says the config.pro in question contains many corruptions.are due to the wordpad that is unable to edit the utf-8 coding without corrupting the data. "I started using the notepad as editor, and "talk" that those problems have disappeared.
two considerations:
1 - in wf3 I used wordpad and never had such a problem
2 - the macros I had, apart from corruptions, work perfectly also in creo 2
Did any of you have any such problems?