![using wordstar for windows on windows 7 using wordstar for windows on windows 7](https://windows-cdn.softpedia.com/screenshots/Psiphon_7.png)
* wxWidgets has GetPartialTextExtents() which, when passed in a string, will return an array of character widths. If all works out, there will be a WordTsar 0.2 Release xxxx happening next week for Linux, Windows, and MacOS. I’ll be testing the Qt version over the next week by editing a 92,000 word novel and bringing that up to 100,000 words or so. What this all comes out to, is under wxWidgets, laying out a 111,000 word document took 1670 ms. I was planning to optimize the dot command routines to speed things up, and I still will (via some form of caching), but I can postpone that work now. Parsing WordTsar dot commands (string heavy) on a 111,000 word novel took 1060 ms under wxWidgets.
![using wordstar for windows on windows 7 using wordstar for windows on windows 7](https://crack4windows.com/thumbnail?path=%2Fcontent%2Fimages%2Fscreens%2Fwordstar-command-emulator-for-microsoft-word_1.png)
Under Qt, which can only measure individual character widths* the speed is 138 ms.
#USING WORDSTAR FOR WINDOWS ON WINDOWS 7 CODE#
With the code optimized to measure strings instead of characters, I got that down to 460 ms. Under Linux, measuring the widths of 605,814 characters took roughly 1800 ms.
![using wordstar for windows on windows 7 using wordstar for windows on windows 7](http://www.wikihow.com/images/c/ce/Install-Audio-Drivers-on-Windows-XP-Step-20.jpg)
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.Actual UTF-8 data entry from keyboard has not been tested, just copy from web to WordTsar.Yeah, a lot of corner-cases from moving to UTF-8.New DOCX loader (incomplete, but not bad).New RTF loader (less complete, but more robust).UTF-8 Backend (see below for tech details).I’m still calling it pre-alpha because I’ve only really run it on Linux (quite extensively). This is the first stable release with a complete UTF-8 based backend.
#USING WORDSTAR FOR WINDOWS 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.