Re: [protege-user] Issue with Displaying Data Properties [SEC=UNOFFICIAL]
Michael DeBellis <[email protected]>
| Newsgroups | gmane.comp.misc.ontology.protege.owl |
|---|---|
| Message-ID | <CALGFike5CCcBnqw4W7FhVasO3uie2gfMnBETheuqwAw_u1q8AA@mail.gmail.com> |
Damian, thanks very much for replicating the problem. It is actually comforting to know there isn't something unusual with my environment. That's interesting about how the resize is what changed it. I assumed it was the extra screen real estate, but what you describe is also consistent with what I observed and makes sense. I'll create an issue on the Protege GitHub site. Michael On Wed, May 7, 2025 at 3:48 PM O'Dea, Damian MR via protege-user < [email protected]> wrote: > *UNOFFICIAL* > > Michael, Samson, > > > > I have managed to replicate the issue. Windows 10 > Enterprise (VMWare Desktop), running Protégé v5.6.0. > > > > I loaded your Display Bug Test ontology, Michael, and initially could only > see the one description value (Capture-01-default sizing.PNG). Sorry, > that’s a poor snip which doesn’t show the lack of a second property being > displayed. :-/ > > > > Instead of going full screen, I just dragged the edge of the Entities pane > left to reduce it, and this resized the rest of the panes. The resize > caused the second property to now be displayed (Capture-02-post > resizing.PNG). > > > > So this could be a longer-standing bug than originally thought (i.e. it’s > not specific to v5.6.4/3). > > > > Cheers from early morning Australia, > > Damian > > > > > > *From:* protege-user <[email protected]> *On Behalf > Of *Michael DeBellis > *Sent:* Thursday, 8 May 2025 7:56 AM > *To:* User support for WebProtege and Protege Desktop < > [email protected]> > *Subject:* Re: [protege-user] Issue with Displaying Data Properties > > > > *⚠* *EXTERNAL EMAIL: *Do not click any links or open any attachments > unless you trust the sender and know the content is safe. *⚠**.* > > I cannot reproduce your problem on a Mac or on a Parallel instance of > Windows 11. On the Mac, I have Protégé 5.6.4, while on the PC, I have > Protégé 5.6.3. On the PC, I made the window about 4” x 6” and even smaller > on the Mac. In both cases, both “description” data property assertions were > displayed. > > > > Samson, thanks for checking. I still think it could be a bug rather than > something with my implementation of Protege. First, it doesn't surprise me > that it works with a Mac. I've experienced that before, a UI feature works > on the Mac version but not on the Windows version. Second, I'm running > Protege 5.6.4 and this is such an obvious issue I think it would have shown > up if it had been around for a while, i.e., my guess is most likely > (assuming it is a problem and not something unique to me) it is something > new to 5.6.4. I have another machine running Windows 10, I'm going to try > this on that machine and see what happens. When I have a chance, I'm also > going to restart my Windows 11 computer. I really doubt it but you never > know, it could be some glitch. I already tried restarting Protege and still > have the same behavior. Let me know if you have any other suggestions. > > > > Cheers, > > Michael > > > > On Wed, May 7, 2025 at 2:39 PM Samson Tu <[email protected]> wrote: > > Michael, > > > > I cannot reproduce your problem on a Mac or on a Parallel instance of > Windows 11. On the Mac, I have Protégé 5.6.4, while on the PC, I have > Protégé 5.6.3. On the PC, I made the window about 4” x 6” and even smaller > on the Mac. In both cases, both “description” data property assertions were > displayed. > > > > *With best regards,* > > *Samson* > > > > On May 7, 2025, at 1:46 PM, Michael DeBellis <[email protected]> > wrote: > > > > I ran across what I think is a bug but before posting an Issue on GitHub I > wanted to check if people have seen this with other ontologies or it might > be something unique with mine. The problem arises when I have two long > string values for a data property called description. When I added the > second string it didn't show up in the Property Assertions window, even > when I scrolled down to the bottom. I checked the Turtle code and sure > enough the second string was there. I played around with it a bit more and > found that when I made Protege large enough to take up my whole screen, > then the second value was displayed. I'm not attaching the ontology because > it is fairly big but it can be found at: > https://github.com/mdebellis/Climate_Obstruction/blob/main/data/climate_obstruction_5-6-25.ttl > > > > > Actually, I decided to try an experiment and created a test ontology and > did the same thing and had the same behavior, so either something is wrong > with my installation of Protege or it is a bug (probably the latter). I'm > attaching the example. You should be able to re-create it by just opening > the ontology and making Protege small enough so when you display the > property assertions on thing1 you can only see the one description without > scrolling. Then the second description value on thing1 won't show up, but > if you make the window big enough so both assertions can be partially seen, > then you should get both. > > > > I'm using the latest version of Protege on Windows 11 Pro. > > > > The Individual is ExxonMobil. In this first screen capture you can see the > beginning of the first description property: > > > > <DescriptionDisplayBug1.png> > > > > Here is the second screen where I scrolled down to the bottom This is when > Protege was only taking up about half of my desktop screen, and there is no > second value for the description property visible: > > > > <DescriptionDisplayBug2.png> > > > > Here is the same Property Assertion view when I made Protege large enough > to take up the whole screen for my Desktop, now you can see both values > show up. My guess is that for some reason, because the Property Assertion > View wasn't large enough to show them both, the second value wasn't > displayed at all, even though it should have been when I scrolled to the > bottom in the first case: > > > > <DescriptionDisplayBug3.png> > > <Display Bug Test.ttl>_______________________________________________ > protege-user mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/protege-user > > > > _______________________________________________ > protege-user mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/protege-user > > _______________________________________________ > protege-user mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/protege-user > _______________________________________________ protege-user mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/protege-user