Hi,
as a part of learning ProjectWise 365 and iTwins ecosystem, I am trying to create iModel using iTwin Synchronizer,
Everything seems to be fine (project is created, empty i-model is created, everything is recognized by installed synchronizer), but regardless I try to add .dgn or .dwg, I always end with:
But the bridges for .dgn (MicroStation) and .dwg (civil / civil 3d) are installed already:
I ensured I have all necessary privileges: Because I am BDN member (I played with iModelJS source code already ;-) and I have all roles assigned both at general and project level, I assume this part should be fine.
Attached are iTwin Synchronizer log files. Windows 10 with all updates and patches installed, Czech GUI and local used.
BTW From log files, it seems Squirel tries to access MS Team. Why?
With regards,
Jan
iTwinSynchronizer Diagnostics 2020-04-20T05-17-47.362Z.zip
Unfortunately, if I had to guess, the Š in your user name is influencing the problem. I'll try to reproduce from that angle.
When you say squirrel is accessing MS Teams, are you referring to the SquirrelSetup-Global.log file? The 'Global' squirrel log may include logging from any squirrel update-based application. MS Teams uses a variant of squirrel for its update technology, so there may be references in there for when MS Teams last updated.
Hi Jeff,
Jeff Marker said:Unfortunately, if I had to guess, the Š in your user name is influencing the problem. I'll try to reproduce from that angle.
Thanks for the explanation! Please, do not tell me there is an application not able to handle Unicode characters in 2020 :-(
You are probably right, because in SquirrelSetup-Global log, based on your info, I found
CheckForUpdateImpl: Couldn't write out staging user ID, this user probably shouldn't get beta anything: System.IO.DirectoryNotFoundException: Část cesty C:\Users\JanŠlegr\AppData\Local\iTwinSynchronizer\packages\.betaId nebyla nalezena.
... which is localized message of System.IO.DirectoryNotFoundException: Could not find a part of the path exception.
Of course the path C:\Users\JanŠlegr\AppData\Local\iTwinSynchronizer\packages\ exists, as well as .betaId and RELEASES files.
C:\Users\JanŠlegr\AppData\Local\iTwinSynchronizer\packages\
.betaId
RELEASES
BTW It's true Bentley systems do not like national characters often:
Jeff Marker said:The 'Global' squirrel log may include logging from any squirrel update-based application
I do not know Squirrel, so that's new information for me. Thanks!
Regards,
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I have confirmed this is the case and will prioritize a fix.
Jan Šlegr said:application not able to handle Unicode characters in 2020
If it relies on Microsoft libraries then there are very often problems. Still not found how to handle local characters in VBA for example if Windows locale is set to English.
How did software GUI become user-friendly? Easy, just replacing in documentation that it has now a user-friendly interface. Same goes for unicode support in applications...
Oto said:If it relies on Microsoft libraries
I think only partially: iTwinSynchronizer has been written from scratch (it's the part where the exception is reported), but I am not sure what technology is used (maybe something Chromium based?).
IModelBridges are based on MicroStation technology, because they have to read and interpret source DGN data in the same way as MicroStation (or any discipline product like ORD) does.
Oto said:Still not found how to handle local characters in VBA for example if Windows locale is set to English.
I am not aware of any such problem, maybe MicroStation Programming forum is better place where to discuss it. But it's true that VBA is old and obsolete technology, designed before Unicode and standardized national specific handling mechanism were standardized and implemented into core technologies.
I tested the workflow with 1.0.112, unfortunately the bug still exists.