No disagreement that we need to fix this. There is a lot going on in this dialog beyond just typing data in cells. First, population values in NORMA always resolve back to an underlying ValueType at some level, so there are existing values to choose from and match. Secondly, you get the issue of complex identifiers (nested complex identifiers, ...
ValueTypeValueRange appears when you have a collapsed reference mode pattern on an EntityType. In this case, there are two collapsed locations where you can attach a ValueRange. The first location is on the far identifying role and is controlled by the ValueRange property. The second location is on the ValueType itself. This is the location ...
Sure. This should only happen with a bad uninstall, or if you've built from sourcecode previously on the machine. This particular entry was incorrectly added via setup in the past, so may be hanging around on some machines. The issue is two extension namespaces mapping to a single loaded extension DomainModel. It blows up badly when an attempt ...
The issue should be fixed with changeset 1292.
Selection behavior from the FactEditor was a difficult choice, and the decision to not select was not done lightly. The issue is that the Fact Editor can also be used to edit an existing (selected) FactType, so a subsequent entry meant to add a new FactType would mean that the current one was edited instead of a new one being created. Note that ...
This one shouldn't be there, delete it and restart VS. This was an ealier name for the Custom Properties extension and was dealt with incorrectly a couple ...
A couple of questions for both of you:
Could you send me the contents of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Neumont\ORM Architect\Extensions key?
Could you launch VS2008 as an administrator and see if the problem still reproduces?
Those would both help me to track down the right machine configuration to test on ...
[quote user="Brian Nalewajek"]In what may be a related issue, I see ternary fact types listed as entity type objects, under the Object Types listing of the Object Browser.[/quote]
All n-ary and spanning binary FactTypes have implied objectifications, which are part of the model. From a FactType selection you can always tell which ...
Welcome to NORMA.
We haven't yet included the UUID datatype, but we should eventually do so. This is a little harder than, say, bigint because not all generation targets support it. Also, we've currently built the autoincrement and identifier notions into a datatype, when in fact the notion of datatype and autogeneration need to be ...
It just isn't done. This was next on my list, after some name generation issues and fixing the unary binarization pattern. This is the easiest of the blatantly undone sample population issues--as has been noted in this thread, the identifier from the supertype is not recognized.
The other major undones for entering sample population ...