View Single Post
Old 02-28-2017, 10:50 PM   #63
Trane
Groupie
Trane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensionsTrane can understand the language of future parallel dimensions
 
Posts: 165
Karma: 51147
Join Date: Dec 2016
Device: android tablet
Quote:
Originally Posted by DiapDealer View Post
Yes. That would be consistent with Book View behavior. I try to edit as little as possible (meaning never) in Book View.
The thing is, I place a picture (in Code View) then I have to make sure it all looks okay, and invariably I see something I could polish up a bit, so I just do it in BookView quickly b/c that's where it's easiest to see how it's looking and flowing.

IOW, I hear you, but I will not stop polishing in Book View. It's much faster and more efficient, for me, using that mode, than having to look past all the code. It's also much easier on my eyes. Today I worked 10hrs on it, minus the time spent here. I can't look at that font/code for 10 hours, it's too much eye strain. I would rather use CTL S constantly even if it means Sigil crashes regularly. But I hope that won't be the case.

I am hoping generating a new .ini -- which also put the temp directory in the native spot -- will do the trick.

EDIT: But that IS why I go into Code View to place an image and write the code around it (img class, figure caption, etc.) That's my compromise.

Last edited by Trane; 02-28-2017 at 10:52 PM.
Trane is offline   Reply With Quote