On Sun, Apr 23, 2023 at 7:19 AM Thomas Passin <[email protected]> wrote:
> uAs would avoid the need to put an image file in another directory, where it could get separated from the outline. This separation (and a need for uAs) could be avoided if we had an archive format for Leo outlines. Maybe images could be cached so they would reload faster while Leo has the outline open. I think this is a separate issue. > As for the magic byte, Qt is going to put it there when the image is inserted, and that byte is going to be associated with a private bitmap stored invisibly by Qt outside of the text content. So these bytes will need to be managed on every reload. I agree. > We would also want to make sure that the image does not get re-inserted unless the magic byte becomes moved away from the position of the *@embedded-image* directive. Otherwise I suspect that the latency after a few keystrokes would become annoying, especially if a node contained several images. A straightforward prototype should reveal whether there are any such problems. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3iHtz%3Dssi9yLikq%2BfzH%3DG59VSmUkE-SU%3DOhos57kb8gA%40mail.gmail.com.
