I’m using S3 on W10 desktop and a touch screen laptop. I’m also using ProWritingAid alongside it.
This works nicely on the desktop but is a nightmare on the touchscreen. PWA scrolls by touch - as it should - but S3 doesn’t. It highlights instead of scrolls, which could be useful at times except that it won’t highlight beyond the displayed page top and bottom (ie, does not invoke scroll).
Worse, I have to try to scroll by sliding the scroll markers in the margins, which at high resolution on a small screen are almost impossible to pick up. Mostly, I pick up scenes instead and slide them out of sequence, and it can be a big job finding out which scene got slid where. And should I slide a chapter into child relationship with another chapter, I cannot put it back without going over to the desktop. By touch, it seems a child cannot be moved up to parent.
This is messy, amateurish and annoying. I’m now using S3 as a container and working on each scene in PWA instead, copying out and back again when I’ve finished work.
Is there a fix, or could you guys pull your fingers out and make it work properly?
If I remember correctly L&L stated quite clearly that V3 was not being written for touch. Could have been something to do with the development environment. So, nothing amateurish about it.
Personally, after having tried a couple of touch Windows devices, I’d characterise Windows touch implementation as amateurish. W11 Is an improvement, but still somewhat a ‘sows ear’, IMHO.
I’m a writer and I love the structure allowed by Scrivener, the way I can build my story scene-by-scene and access all my research and my notes. But i’m a creative, as we all are, and I love to do my creative work away from the desk; in a cafe, by the riverside, on holiday. For this i use my 13" Zenbook, an excellent bit of kit. It works only because it has a touch screen. I need no mouse, no flat surface, i don’t have to fiddle with a stupid mousepad. But because, of all the apps I use on it, S3 is the only one which doesn’t support touch, I forget to scroll with arrow keys and instead, end up picking u a scene and dropping it into the void, having to spend ages when i get back to my desk trying to find it again and rebuild the structure.
I suggest that not supporting touch screen in a creative program is remiss, especially when there are many other writer’s apps out there.
Perhaps to clarify, not support touch at time of release of V3. Their main thrust was to achieve as close to parity as possible with Mac V3 and MacOS is not touch. Of course the VAST majority of Win devices are also not touch. There are thousands of Win apps that do not fully support touch.
I can’t speak for L&L, but that’s the current situation. As the initial V3 bugs are ironed out and the development team begin to have free time, it may be touch becomes a focus.
Yes there are many other writers apps out there and you are free to move to any of them. Your decision would be, does touch support outweigh the lesser functionality/added cost etc of them.
Personally, when I had my Surface Laptop I found touch to be a Total pain in the arse, regardless off app, but that’s just me.
I have a Windows 10 laptop with a touch screen. This laptop is five years old. I doubt the “vast majority of Win devices” that writers use do not have touch screens. Even if it is true, I’ll bet there is a “vast minority” of touch screen devices running Windows, and that minority will grow over time.
Touch screen scrolling works in Scrivener 2, which I use for old projects, but it doesn’t work in Scrivener 3, which I’m using for new projects. This is a MAJOR step backward.
I’ve had the same problem, but just discovered that S3 will scroll by touch IF I use 3 fingers together. I have an RSI aggravated by using a mouse. Scrivener removing normal touch support is ridiculous.
If I remember correctly, they didn’t ‘remove’ touch, it was never there as such.
V1 wasn’t written for touch, but apparently did work.
V3 I seem to remember some issue with support for touch on the development platform so it wasn’t on the release. L&L may want to comment on the current status.