Yes, I am aware of this setting but thought it only affected instances and not
the Classes view. I can check, but I normally up this value to 10,000. It might
be back down to 1,000 which, if memory serves, is the default.
--
You received this message because you are subscribed to the Google Gro
Oops, I noticed too late that Richard had already responded along the
same lines. Too many emails this morning :)
Holger
On 8/06/2018 8:29, Holger Knublauch wrote:
Hi Jack,
I checked the source code of the classes tree and it does have a
maximum number of children, which is the value that
Hi Jack,
I checked the source code of the classes tree and it does have a maximum
number of children, which is the value that you can configure in TBC
Preferences > Max number of instances to display. Could you try
increasing that number to check if your classes then show up?
Holger
On 7/0
This default may be involved in counting the number of class instances that is
shown next to each class in the tree.
How may classes do you have, Jack? I have not experienced this problem and I
commonly work with ontologies that have hundreds of classes. I just checked
FIBO. It has over 4K clas
Jack,
Are you aware of this:
Preferences > TopBraid Composer > Max. number of instances to display
This setting is used in a number of places in TBC to limit the number of items
shown. It is also involved in populating the tree, although I am not sure in
what way exactly.
Richard
> On
That ontology has existed for several years and is in use in various projects
so yes it is connected to owl:Thing and to rdfs:Class. But it occurred to me
that perhaps the superclass of fonm:Concept, which is prov:Entity, might not
have a prefix in the current graph so I created one and that did
So are you saying that the classes in the dialog (e.g. fonm:Axle) are in
the file but cannot be found in the classes tree? How are those classes
defined, e.g. are they connected to the root class via any
rdfs:subClassOf path? Maybe they cannot be reached?
Holger
On 7/06/2018 9:23, Jack Hodge
It's probably crashing in the middle of the selection operation, for yet
to be determined reasons. Do you see anything in the Error Log? Is there
any chance you can send me a copy of the file(s) in question off-list?
Holger
On 26/04/2018 10:06, Jack Hodges wrote:
Yesterday I encountered the m
Yesterday I encountered the most unexpected and undesired condition. I have
2 ontologies that are the basis of a third, bridge ontology. If I load
these two ontologies into TBC they load fine. If I import them into my
bridge ontology and load it, the bridge classes (etc) show up in the
classes