I tried it too, and could not reproduce it. I had an Intent design, inheriting from IvDrawingSheet, blank sheet showing in Inventor. In the Design Editor, I tried adding "view" Child rules, using "." in numbers, and it all worked. Sorry!
(It worked OK in ETO Studio -- Visual Studio, too.)
I have an idea. Is your operating system not en-US? Is your installation not en-US? This might be why we cannot replicate. And since the failing thing appears to be some kind of string comparison, it might be related.
Could you please to see this video.
I have en-US version. Our company is located in California.
I don't understant why I have this issue after reinstalling ETO. Before I didn't have it and I didn't change Intent code.
The problem is just with numbers.
We don't understand, either. I could not read anything in the video, but I see that you tried several files and only one has the problem. But this file has a LOT of content. It was not what you described as steps to replicate, which Jon tried to follow. Can you send me that file? All the evidence is that there is something about this particular file. Even if you can get it to happen with ANY file, send the failing file to Jack.Gregory@Autodesk.com.
I know this is painful, but these kinds of things usually are. There is something here which we did not see in testing, and we need to understand.
Also: You said it fails in ETO Studio. Can you send me the backtrace for that failure as well? We can take this off the discussion group and then report back to everyone when we have something.
I tried recreating the error from what I understand. I used the SheetMetal assembly in the ETO 2013 samples. It has a drawing. In the design for SMDrawingSheet I tried entering the double for values. (.22, 0.4) I attached a screenshot to show what I did.
Can you upload a small dataset that I can use to recreate this error? Another screenshot of your ETO dialogs would help too.
A little bit wrone. I don't have any problems with particular file. The problem is when I try to modify the sheet design file and have active drawing what has been created from this sheet design file. I have 25 drawings and 25 sheet desing files respectively. When I generate any drawing through the Intent I have issues with sheet design file that has relation to active drawing. If I close drawing I can do with sheet design file whatever I want.
In previous post I have saw screenshot, hovewer, it's Visual Studio, not Intent Design Editor.
The AVI you posted to drop box is of Intent Design Editor. It fuzzily shows that in the Title Bar.
In Design Editor, in the View menu, there is a check box to turn Intellisense off. Could you uncheck that and see if you have the same problem? If you still have an exception, please send the full backtrace so we can see what is different.
I have tried to turn off intellisense. No changes. I can send to you my sheet design file, but I'm not sure you can run it. We have a difficult design structure. We use own application for working with database. I mean transfer all needed variables from database through this application. Build 3D model and set of drawing runs from application as well. I tried to use Visual Studio, hovewer, Intent model didn't load into VS. One more thing. We have 2 the same machines what using the same Intent design files. On my machine has been installed ETO R2, on the second machine - ETO R1. On my machine exist this problem, on another machine not.
After many trials and guesses, we have replicated this problem. It occurs when there is a conditional child rule (the Design is conditional). It is also a separate defect that turning Intellisense off does not stop the problem from happening. The problem has nothing to do with drawings. It is replicable with a trivial Design.
This problem is not present in ETO Studio. That is the recommended workaround until a fix can be released.
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!