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 ...
This was eventually "fixed" by launching VS2008 as an Administrator on Pat's machine. We have not managed to reproduce this problem on other boxes, but would like to know if it happens for others as well. The weird thing is that the 'PropertiesEditor' property, which is appearing correctly, is displayed using the same ...
Wow, ancient bug (Dec 2005), nobody noticed. Basically, the role player for the role opposite the internal constraint was being verbalized instead the associated 'PreferredIdentifierFor' relationship. I've fixed the bogus verbalization in changeset 1288, added a small indent to the 'This association...', and added the same ...
We're putting final touches on a new sourceforge drop, which will be available next week. The new drop features much better name generation defaults. Among other things, we allow you to control how the reference mode name is used in both references to entitytypes (mapped to columns with a foreign key, or fully absorbed columns) and for the ...