Keeps turning into code view

[automa]

I'm reading an old book and trying to turn all the "chapter" into h2
But when I do a find for 'chapter' it turns the book view to code view.

[patrik]

As I understand it the find searches in the actual content in the file, not from how the text is presented. In other words, it always searches as if the file is as it is in "code view" (which is how the file actually is). And to show the result, therefore it must enter code view.

For example, say you to a find for <h1>. You probably don't have that in what the reader sees, but it's probably in the code showing the chapter title. And to be able to show you where it found it, it must enter code view.

There is a reason that most experienced Sigil users always use code view (+ preview) and not book view. (I'm slowly adjusting to that myself...)

[theducks]

Originally Posted by automa

I'm reading an old book and trying to turn all the "chapter" into h2
But when I do a find for 'chapter' it turns the book view to code view.

FWIW I mostly use the Preview Pane for viewing, rather than Bookview
That said, I think S&R works on Code View only. When it lands, the Preview will sync

[automa]

It used to not do that. It was better because there are description following the 'chapter i' chapter ii' etc that I need to place next to the 'chapter i', which then automatically become an h2 instead of an h7 that it was, so that I can see what the chapter is about when reading on my phone.

It doesn't automatically do that on the code view. I have to highlight it first and then do CMD 2 to change it into h2.

However looking at the code view, is there a way using the code view or the book view to change the font, font color, and highlight a part of the text with a color?

[theducks]

Originally Posted by automa

It used to not do that. It was better because there are description following the 'chapter i' chapter ii' etc that I need to place next to the 'chapter i', which then automatically become an h2 instead of an h7 that it was, so that I can see what the chapter is about when reading on my phone.

It doesn't automatically do that on the code view. I have to highlight it first and then do CMD 2 to change it into h2.

However looking at the code view, is there a way using the code view or the book view to change the font, font color, and highlight a part of the text with a color?

Permanent?
Stylesheet and a saved search (for each combonation.
eg
Saved Clips (make appear on the toolbar)

<span class="yelBG">\1</span>

The Stylesheet entry:

span.yelBG (background-color: yellow}

This style Save Clip applies to the selected text. the secret is th \1

[DiapDealer]

Originally Posted by automa

It used to not do that.

The current behavior has been in place for many, many, many, many versions.

And it's only "All HTML Files" or "Selected Files" that will automatically switch to Code View. You can still use "Current File" to search Book View.

[BetterRed]

Originally Posted by DiapDealer

You can still use "Current File" to search Book View.

Never knew that! Not that I ever use BV, it was years before I even knew BV and PV weren't different names for the same thing.

BR

[JustinThought]

Originally Posted by DiapDealer

The current behavior has been in place for many, many, many, many versions.

And it's only "All HTML Files" or "Selected Files" that will automatically switch to Code View. You can still use "Current File" to search Book View.

Originally Posted by BetterRed

Never knew that! Not that I ever use BV, it was years before I even knew BV and PV weren't different names for the same thing.

BR

New to me, too. But IMO, it's easier to just do the search, which of course comes back in Code View, and if I must see the Book View (like most everybody else who has expressed their opinion, I usually keep Code View open in the middle and Preview on the right), just double-click the tab at the top. Nice feature, that little toggle, for a lazy man like myself.

[theducks]

The one time I (try to) use BV, is when I get a Pink Box error in CV or when I save and it complains. I switch to BV and start switching (open)Tabs until I hit the problem file.

I select Fix Manually, and it takes ne to where the error was discovered (usually a missing Close tag, or I removed the Open tag )

[DiapDealer]

Originally Posted by theducks

The one time I (try to) use BV, is when I get a Pink Box error in CV or when I save and it complains. I switch to BV and start switching (open)Tabs until I hit the problem file.

I select Fix Manually, and it takes ne to where the error was discovered (usually a missing Close tag, or I removed the Open tag )

The F7 check will quickly identify which file, as well. Handy for when a find/replace or plugin result has gone pear-shaped, but you're not sure which file is the problem.

[theducks]

Tnx I will try that the next Pear