Jump to content
Storyist Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About warrenao

  • Rank
  1. I'm not actually sure what to call this. When I'm in draft mode, all the pseudomargins go away — top and bottom, left and right. That's fine, because I don't want or need them there. However, the entire view becomes larger by maybe 20%. The reason that's inconvenient is that I have fewer lines of text on screen then, since the text size has been scaled up. What I'd like is for draft mode to be magical, in that it magically knows not to scale text, so I don't have to manually reduce the size of the typeface in order to fit more lines of text on screen. Screenshots to illustrate what
  2. And heck, I put this in the Storyist/Mac troubleshooting forum. Apologies.
  3. I done founded me a bug. When using Storyist on iPad in draft mode, any line of text on the screen that would ordinarily occur at a page break is not directly selectable by tapping. What appears to be happening here is the draft mode page view, when it reaches the "end" of a given page, doesn't quite seamlessly overlap with the "beginning" of the next page. My workaround is to add a return or two above the place where I want to tap to select. I've attached a couple of screenshots to illustrate what I mean. Here, I'm working in draft mode. The insertion cursor is located at
  4. Resurrecting a feature request from 2008 (!) here: http://storyist.invisionzone.com/index.php/topic/413-password-protection-for-storyist-files/ Since we have an iOS flavor of Storyist now, and since it is conceivable (via Dropbox integration) that Storyist file contents could be illicitly accessed by third parties, I'd like to see a setting that lets users activate encryption on their files. There are stacks and heaps of good encryption algorithms out there; a nice strong one might be Blowfish, and I believe that OSX/XCode have Blowfish algorithms built in. The way I envision i
  5. I wrote code for a number of years, so Ah Feel Yer Pain. If you want a beta tester I can give it a shot. And no, I didn't think it would be quite as easy as loading an environment specific component; that would be a little too obvious and backward-compatible for Apple. This is, after all, the same company that left iPad v.1 out to dry after just one year. I was just hoping, as I do, because otherwise aaaaaaaaaaaaaaa.
  6. And you can usually trust me to find the problem, whatever it might be. Sigh. I don't suppose it's as simple as querying the OS environment on load, and linking to the correct text renderer based on the result?
  7. Storyist 2.4.5 (1891), OSX 10.9.1. AFAIK everything is current. I don't see kerning hiccups in any other program that uses OSX's native text renderer.
  8. Hello again! Mostly I'd like to be able to set a few keys of my own. Em dash, ellipsis, and typographer's open/close quotes are the most useful to me, since all of those keys are buried under multiple strokes in the iOS keyboard, and I prefer to be able to add them myself, directly, rather than rely on software to interpolate it for me. A typographer's apostrophe would also be groovy, as would easier access to asterisk and bullet characters. I'm thinking if there were a way to let users set their preferred extended keys, it would be more flexible for all users, not just those of us who
  9. Hi, Steve! Thanks for taking the time to reply. I've attached a screenshot here that shows Storyist's text rendering on the left, and TextEdit's on the right. I've highlighted a specific word in each document window that illustrates the kerning problem I mean. As you can see, the letter spacing in Storyist doesn't have the same kind of hinting as what TextEdit does; and you can see that it's a consistent problem throghout. The typeface is Helvetica in both documents, but this problem happens in all proportional-width typefaces I try in Storyist, such as Georgia, Verdana, Times, etc. It loo
  10. This has come up once before in the fora, as far as I can tell, but the kerning in Storyist for Mac is … apparently nonexistent. I realize that's probably a somewhat esoteric concern for some, but a properly kerned page onscreen makes the difference between smooth readability for editing, and having your eyes hang up on strange spacing between C's, L's, and O's (for instance). I'm aware that some typefaces, such as the monospaced ones, don't have this problem, but I don't find monospaced type particularly readable in any circumstance, particularly on any kind of screen. To me it looks
  11. Howdy, all. I'm still noodling about with Storyist, having been drawn to it because I like the idea of retaining my formatting across platforms (Mac / iOS) and having the hierarchical structure that lets me organize my work by chapters and sections in a way a linear text editor does not. So my question. On the iPad, the keyboard has that row of extended keys - cursor motion, single and double quote, etc. What I'd like to know is if I can customize those keys and, if so, how. For instance I'd like to have a typographical open and close quote option (specifying “ and ” as custom-set keys in
  • Create New...