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 Hodges wrote:
I dropped this problem for a while while I worked on other things but
it is very frustrating. I checked all of my imports and they are fine
(well of course they are or I couldn't search on and find the
classes). I checked my namespace prefixes because that can affect what
shows up in the Classes view but they are all fine also. Then I
thought "maybe there is a numeric limit of how many classes can be
shown in the Classes view" but I couldn't find anything like that in
the Classes portion of the Preferences. So it is a mystery. I have
attached a screen shot of the problem. The screen shot doesn't show
the imports or prefixes but they are ok. Oh, I labeled the figure as
being from v5.4 but it is all of the versions I have been using
lately, including v5.5.
Jack
On Wednesday, April 25, 2018 at 5:14:00 PM UTC-7, Holger Knublauch wrote:
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 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 browser, along
with the classes of one of the imports, but the classes of the
other import do not show up. If I do a search in the classes
search area they show up in the search selection dialog, but if I
select one nothing happens in the classes list (whereas normally
it will open the tree view to the selected class - as you know).
There are no issues with the imports tab; everything is importing
just fine.
This is only happening with a specific ontology that I imported
from XML using TBC.
Has anyone encountered this kind of behavior in TBC, ever? Any
pointers would be most appreciated.
Jack Hodges, Siemens
--
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected] <javascript:>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
