We’ve added caching that should get around that.Ĭarat movement is all grapheme based. We now use a plain buffer per paragraph, and have seen some slow downs because of it. Adding UTF-8 support added created issues with the single buffer issue. Don’t ask me why, I can’t remember.Įvery version of WordTsar has been using a gapbuffer for it’s underlying document buffer. I reset the build number for this release.
#Does wordstar for windows run on windows 7 update
I released it with RTF file saving turned off, so I deleted the release and did a quick update to 0.3.313 with that error fixed. If you insert new fonts during editing and save, those new fonts will be converted to Courier or Times New Roman, since the only information Qt gives me is proportional or monospaced. I haven’t figiured out how (or if) I can do that in Qt yet.Īny Wordstar file loaded with font information will saved with that font information intact. With WxWdigets, I was able to find out is a font was serif or san serif, proportional or monospaced, and even what codepage it was from. Switching from WxWidgets to QT lost us some granularity on fonts. This is a bug fix only release, and all users are recommended to update.įixed Tickets #36 Catch Window close to possibly save fileįixed Tickets #35 DOCX incorrectly says it can save filesįixed Tickets #34 Wordstar save fonts failingįixed Tickets #32 Crash on macOS when exitingįixed Tickets #30 page break spacing while editing RTF and DOCX File IO isn’t unicode aware yet either. This is marked as pre-alpha because of the Unicode backend changes… it is stable for me, but I don’t do a lot of Unicode work.
0 kommentar(er)
