I’ve searched the EpiCare site and found a “KB” stating there isn’t a global way to change the size of fonts in dashboards/forms other than personzalizations on each of them as of version 10.
Does anyone know if there has been an update to that within Kinetic? We are currently on 2023.2 while we try to work out our customizations to take that next leap to 2024.1, but was curious if this was addressed in future releases since version 10 for those of us that need extra sets of eyes to view screens.
I would think once you get to the browser, the font size can be adjusted as a normal browser +/-, but was curious if there was anything between version 10 and 2023.2.
Asking for a friend AND myself!
Thanks, and stop laughing! Someday you will go blind like the rest of us!
I’m right with ya. I’m to the point where I used to need glasses to read, but now finding now I don’t, but still for distance. How does THAT happen?!?!?!
Hi Jason,
Yes, we are still using the Modern/Classic forms for now until we can get to re-writing the boatload of customizations we have currently to make sure they will work in 2024.1. lol
We are “that close”, I know, but it’s going to take a while to get there, unfortunately.
We’ve started with our customized dashboards, and then we are going to move to Trackers before attacking the Forms.
Well, I know it’s been asked for a lot over the years, but I wouldn’t know if there was ever anything to address the classic UI. I think you’re as much a regular on here as me. I don’t recall ever reading anything.
FYI, several of our users do crank up the size in the browser here.
The irony is that it can cut off a critical part of a Kinetic form - without the ability to scroll to it. For example: dispatching a requisition. Users wondered where the buttons went. You had to unzoom back to 100% to see them.
No idea if they ever fixed that. Was I supposed to report that…?
if you have an example of something going away when you zoom in, we need to know about it. our intention with the screens is that zooming should work (within reason).
In March of this year we were on 2022.2 and scrolling did NOT work, according to a user (I just dug up our internal ticket). But I succeeded in scrolling in 2023.2.
