View Single Post
Old 01-12-2026, 04:46 PM   #27
un_pogaz
Chalut o/
un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.
 
un_pogaz's Avatar
 
Posts: 673
Karma: 720026
Join Date: Dec 2017
Device: Kobo
Quote:
Originally Posted by KevinH View Post
Are you asking for a special syntax color to help identify what is incorrect (but that can not help if something is missing). [...] How much more help does someone need to find an error?
Yes, exactly, highlight the error itself.
I will very prefer it with a undeline wave, 'bigger' than for spell error (so very like in a code IDE), but I let you see how implement it at the end. As long as there is a clear and specific such visual hint, I would be satisfied.

Like I said, the "Validation pane" and the "xmlparsing error" work fine, but it would be sooooooooooooo great to have also a hint in the code view itself.
un_pogaz is offline