Once you've perfected Editorial as is, consider supporting two independent panes in the interface -- two views of the same file, or two different files. Maybe not so good for coding, but for text editing (which is what I do) it would be great. I imagine it could be done in Python, but not by me. Somebody else?
...that appears when I tap "+" to create a new document.
If I create a new text document and rename it with ".fountain" at the end, the app seems to interpret Fountain markup correctly. What do I need to do to see "Fountain (.fountain)" in the list of document templates?
I have a bluetooth keyboard with a full set of keys, including control, option, alt, the 'meta' key.
I'd like to take advantage of these keys by writing keyboard macros or abbreviations, whatever you want to call them) that are triggered by alt-, control-, option- key combinations.
But Editorial doesn't respond to them. The research I did suggests that the software isn't detecting the extra codes thrown by these key combinations.
How about it? Could Editorial be enhanced to capture/handle these key combinations? (Not that I want you to assign them to specific actions -- just make it possible for us to use them to trigger macros, etc.)
(Or: if this is already possible, can someone tell me how to get it to work?)
Editorial's onscreen keyboard has an extra row of "keys" at the top. It's very handy.
When you activate a bluetooth keyboard, the regular onscreen keyboard disappears, but the extra row remains.
The problem: as you type, the cursor goes down line by line toward the bottom of the editing panel. But the last line of the editing panel is hidden underneath that extra onscreen keyboard row. You can't see what you type.
You can keep typing to the end of that bottom line, but the editing panel only moves up one line, so you still can't see what you're typing.
The only thing to do is to press Enter several times to put a lot of blank lines at the bottom; but (if you're just typing text) you just use those up, then you're back at the hidden bottom line again.
Any fixes for this?