![]() The approriate _shortName could be looked up using the enumerated _langID which every Lang instance already has or else the Lang type can be refactored to store it’s own pretty name. Potential Solution: There is already a ScintillaEditView::_langNameInfoArray type with a more readable _shortName member. ![]() Problem 1: cryptic language identifiers in the Tab Settings list boxĬause: the window procedure that fills Tab Settings uses an instance of this Lang structure, which has a _langName member, filled by the name= attribute of langs.xml, which is identical to the Lexilla language identifier so that N++ can send it, unmodified, directly to Scintilla when creating the lexer (convenient for the developer, less so for end users). Me attempt to summarize, hopefully for someone’s benefit, what we know so far: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |