Quote:
Originally Posted by hobnail
Looking at all of the gizmos they announced today it makes me wonder how many of the Kindle programmers wear two hats; one for Kindle and the other for Echo, Fire Stick, Alexa, etc. If so, I'd imagine that Kindle support gets lower priority.
|
They've known that their K4Mac app has a bug--the toc.html doesn't work, past the third entry on the TOC--for 2 years.
I reported the whole, links don't ork in FXL made with KC and some of their other DIY apps, 18-35 months ago (various dates for various apps).
The links don't work thing is pretty simple--the FXL "print replica" is nothing but images. Not searchable text; one image after another.
How can a link work in that environment?
In the old KKBC, you
could make working links on any page, as long as the link itself wasn't in the popup box. Again, same/similar issue; the json was popping up the page, no linking functionality available AND you can't put a link, in an image, in Kindle. (And only remotely successfully make an image AS a link, in reflow.)
That also, btw--for anybody here that gives a s**t about the actual technology, affects how the images work and zoom--because, if you create an image AS a link--which people do--the
activation for the link is DIFFERENT than the zoom functionality.
Hitch