Not great but it scrolls as smoothly as a browser so I’m happy with it for now. If you find a JavaScript library I would be interested, too, because I want to optimise the html that my app creates. Anyone have any ideas about how/why it browses the html viewer the way that it Willius:
Html image viewer full size#
My guess is this is somehow related to Xojo’s handling of the HTML viewer- would that be right? I know, regardless of what size the HTML ( ) loads the image as, the images are being loaded full size and merely displayed smaller but given that I’m working with several thousand images I don’t think that resizing the images is going to be an option because of how long it would take to resize that many images. I’ve got plenty more CPU time and Memory when this happens. When I do scroll the CPU Time eaten up by the debug application spikes as high as 33% (very briefly) and the memory usage goes up to about 300MB and then goes back down to 224MB (for 25 loaded images). Arrow buttons on the keyboard aren’t much better and same goes for the scroll wheel on the mouse. The clicks on the scroll bar don’t show a response for close to 2 seconds.
My problem is that I started with 100 images and I’ve now scaled it back all the way to 25 images (per page) and the result is the same: SUPER SLOW and glitchy scrolling in the HTML Viewer. I planning on using pagination for that but I wanted to use as few pages as possible. It would be common for the browser to need to work with an sd card containing thousands of images.
:max_bytes(150000):strip_icc()/002_view-html-source-in-chrome-3466725-5bef1cdd46e0fb0026a96f2f.jpg "html image viewer")
It’s intended to be an SD Card browser/selector. I’m using Windows and I’ve constructed an HTML viewer that uses a table to load my images. The thread that got me to try the HTML tables was one where it was recommended by Michael Bujardet (it was for iOS). I’ve read several conversations here about people using HTML Viewer to browse or load images.
0 kommentar(er)
