Data Properties May not Be Displayed in Property Assertion View in Protege 5.6.4 on Windows

[mdebellis]

This is Windows specific, Samson tried to replicate this on the Mac and couldn't but Damian O'Dea was able to replicate it on Windows (see the log on the Support for Protege email list). If you have two data property values for the same data property that have large chunks of text and the first one takes up all the screen real estate in the Property Assertions View, when you scroll down you don't see the second value. The first figure shows the beginning of a value for the description data property of an Individual: ExxonMobil. There is also a second data property but as you can see in the second screen capture, when I scroll down it doesn't show up. When I expand Protege to take up my whole screen so both values can be displayed (the third picture) then the second value shows up. Damian also found that if you just expand the Property Assertion view that also makes both values show up and I confirmed that also works for me. I'm running Protege 5.6.4 on Windows 11. Damian replicated the problem running Windows 10 Enterprise (VMWare Desktop), running Protégé v5.6.0.

[gouttegd]

I do not reproduce the problem here. Both properties show up normally.

What I do observe, on all three systems (GNU/Linux, macOS, Windows) is that scrolling using the mouse wheel seems… “weird” as soon as there is a “long” property value (long enough that the entire value cannot be displayed at once, if the window is too small). In particular, a single turn of the wheel makes the scrolling window jump straight to the bottom. This could easily give the impression that some values are not displayed (especially if, as in your example, the two values you expect to see are identical).

Scrolling using the scrollbar (clicking and dragging down the bar, not clicking the scroll down button, which seems to behave like a turn of the mouse wheel) does not have this effect and allows to scroll smoothly and see all the values.

[mdebellis]

Thanks. FYI, in the version I posted the text was the same but in the original example where I first noticed it that wasn't the case. There were two big blobs of text, one an overview of Exxon, the other on their history. And I just tried it again and (when there isn't enough room to see both and I use the mouse wheel) I definitely just see the first overview, it isn't just jumping to the end. I can tell because the overview ends with: "The company has been the target of accusations of human rights violations, excessive influence on American foreign policy, and its impact on developing countries." Whereas the history ends with: "Following the merger, Exxon's NYSE ticker symbol was changed from "XON" to "XOM". I have observed the same thing, it only happens when I use the mouse wheel, so it definitely isn't an issue for me now that I know. But IMO it is still a bug because lots of people use mouse wheels and it gives you the impression that data you entered is not being saved which can be kind of disconcerting. Michael

…

On Thu, May 8, 2025 at 2:17 AM Damien Goutte-Gattat < ***@***.***> wrote: *gouttegd* left a comment (protegeproject/protege#1281) <#1281 (comment)> I do not reproduce the problem here. Both properties show up normally. What I do observe, on all three systems (GNU/Linux, macOS, Windows) is that scrolling using the *mouse wheel* seems… “weird” as soon as there is a “long” property value (long enough that the entire value cannot be displayed at once, if the window is too small). In particular, a single turn of the wheel makes the scrolling window jump straight to the bottom. This could easily give the impression that some values are not displayed (especially if, as in your example, the two values you expect to see are identical). Scrolling using the scrollbar (clicking and dragging down the bar, *not* clicking the scroll down button, which seems to behave like a turn of the mouse wheel) does not have this effect and allows to scroll smoothly and see all the values. — Reply to this email directly, view it on GitHub <#1281 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD7TPBAY4KKXEJEST3QL2RT25MOKVAVCNFSM6AAAAAB4VD3BXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNRSGM2DMOJWGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>