FYI I believe Robotframework-FlaUI is the replacement to White Library, it adds support for metro apps in addition to what White Library did. I only used it once a couple of years ago but it worked well for me.
There is also robotframework-imagehorizonlibrary which is similar to SikuliLibrary, imagehorizon is pure python where as SikuliLibrary is Java based. I submitted some bug fixes PR’s for imagehorizon but there has been no update since, so i’m not sure if imagehorizon is being maintained?
SikuliLibrary and imagehorizonLibrary also have to keywords for getting data but they are essentially limited to double clicking at x,y co-ordinates and copying to the clipboard or doing OCR of a region of the screen to get the text
None of these libraries can give you the level that a library such as SeleniumLibrary can, however if you know the what development framework the application was built with you may be lucky and find a library that works with that development framework and can interrogate that application and give you more detail.
What you could try as rightly so… Whitelibrary doesn’t have the means to grab those property values but as part of your test… you could try to grab that ‘attribute’ property value, is to ‘Activate Application’ Accessibility Insights For Windows (you can switch off always on top so it’s not covering any windows so it never sits on top), and when you come to that element you need that property value for, you could then send the key press for the shortcut to start/pause for Accessibility Insights, then bring to front (I believe there’s a shortcut for this too) then grab that value from the properties section from Accessibility insights, once captured pause/close Accessibility Insights.
You should be able to use two instances of Accessibility Insights, one paused and one active to get the steps needed to automate that windows element’s property value… or if two instances cause problems (you could use the legacy inspect tool as an alternative and Accessibility Insights together).
Just an idea… feels a little dirty to piggyback off the back of that application… let me know if it works though, or if you find a way to get the property values by other means.
I’d suggest before you start trying to use robotframework-flaui try downloading FlaUI Inspect (link from the robotframework-flaui page) as this tool will firstly let you know if robotframework-flaui can interact with the elements of your app, and second you’ll probably want this tool anyway when you want to find the field id’s to automate the application.
If FlaUI Inspect can’t find the elements of your app then you’ll have saved youself installing robotframework-flaui and know you need to try something else.