Huge annoyance when using split screen TEXT/XML

[sdcinvan]

Is anyone else bothered by this...

When using the split screen and editing in the TEXT window / HTML, coding errors are continually 'popping' because of the real-time syntax checking. So, the moment you begin typing HTML, you can't even complete the code before you get an error message. It is kind of annoying. I wish there was a delay or it was smart enough to allow you to complete your thought before displaying an error message.

Otherwise... Happy Friday to all!

[kwag_myers]

If you're referring to this:

syntaxError.png

...then, yeah, it is annoying. However, it has nothing to do with split screen that I can tell. I get it whether I'm using one or two screens. But I've learned to ignore it as it goes away once you complete the edit.

[sdcinvan]

If you're referring to this:

syntaxError.png

...then, yeah, it is annoying. However, it has nothing to do with split screen that I can tell. I get it whether I'm using one or two screens. But I've learned to ignore it as it goes away once you complete the edit.

Hmm... I don't remember it being a problem before I switched to split screen. Incidentally, I am using split screen because I was experiencing a LOT of .NET crashes as a possible consequence of switching between XML and TEXT editor modes. Those .NET crashes have vanished since going to split screen mode.

The Flare editor needs much more intelligent parsing.

[sdcinvan]

I knew there was more to this annoyance.

Here is an example that just happened. It's minor, in the grand scheme of life, but still annoying.

I was changing the width value of an image in the lower TEXT editor half of the screen. But I was too slow... because I was thinking about the exact value I needed.

The trouble is, if you don't enter a valid value quick enough the error message window suddenly appears, like this...
"CSS: D:\_Projects\Flare\770-00010_User_Guide\Content\1s_usingproduct_5support-.htm: CSS: Invalid width: px"

...and the XML view inexplicably jumps to the top of the page. Grrr

[sdcinvan]

I meant to end that message with a
I'm having a good Flare day.

[LTinker68]

There are arguments both sides of this. Yes, it's an annoyance, but on the other hand, it was probably designed that way to make sure you saw the problem before moving away from that line of the code. So having it flash at the top of the screen isn't a big deal, although if you hand-code often then you'll probably just start ignoring it.

The page-behind view jumping to the top of the page is a problem, because it's taken you away from where the problem is, so you should definitely put in a bug report for that, if you haven't already.

[sdcinvan]

There are arguments both sides of this. Yes, it's an annoyance, but on the other hand, it was probably designed that way to make sure you saw the problem before moving away from that line of the code. So having it flash at the top of the screen isn't a big deal, although if you hand-code often then you'll probably just start ignoring it.

The page-behind view jumping to the top of the page is a problem, because it's taken you away from where the problem is, so you should definitely put in a bug report for that, if you haven't already.

Hi Lisa,

I don't know how others feel but for me, the ideal behavior is to just indicate the error and not do anymore.

Also I hope MadCap works on making the error messages more helpful. Sometimes it might be algorithmically difficult to determine and display the correct course of action but other times (such as in this example):

Text_editor_warnings_not_helpful.png

Compare the line number where Flare says the error originates and where the actually error is located. All that is missing is the closing </h2> tag. Surely, that should be easy to detect.

[kwag_myers]

How is the editor to know what is nested and what is not? It's easy for list items, which are always nested in ordered/unordered lists. In your example, I agree that having a paragraph inside a heading should indicate an error (probably at the <p> tag). But I've seen people nest a sub-heading and paragraph inside a paragraph. I can only guess if it was intentional or not. The point is, we don't all follow the same rules for nesting styles.

I can see where this could get really complicated for the developers. I have one table that always shows a warning for non-table items (because I have drop-downs in the table). If Flare developers start adding rules for what can and cannot be nested, I have a feeling I'll be seeing a lot more warnings.

fwiw, when the closing body tag (</body>) is indicated it usually means I missed a closing tag somewhere.

[sdcinvan]

How is the editor to know what is nested and what is not? It's easy for list items, which are always nested in ordered/unordered lists. In your example, I agree that having a paragraph inside a heading should indicate an error (probably at the <p> tag). But I've seen people nest a sub-heading and paragraph inside a paragraph. I can only guess if it was intentional or not. The point is, we don't all follow the same rules for nesting styles.

I can see where this could get really complicated for the developers. I have one table that always shows a warning for non-table items (because I have drop-downs in the table). If Flare developers start adding rules for what can and cannot be nested, I have a feeling I'll be seeing a lot more warnings.

fwiw, when the closing body tag (</body>) is indicated it usually means I missed a closing tag somewhere.

Well, the editor should have, at least, know that I just removed </h2>.

At any rate, I will acknowledge that IMHO, making the editor's syntax checking smarter is not a high priority.