×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
A generic mechanism for customizing the colors of the parsers will be
added to the "LPEX Editor" preference pages.
This aside, any parser can be extended, and then the new parser class
may be used with a new parser name or to redefine an existing parser
name, and associated with the file extension(s) which apply. This can
be done programmatically, or via the "LPEX Editor" -> "Parsers" and/or
-> "Parser Associations" preferences.
Now, *what* exactly can be extended in each parser depends on the public
and protected methods it makes available for this purpose.
Bartell, Aaron L. (TC) wrote:
Could LPEX extensions be written to accomplish some of the requests we have
submitted to FRED? For instance, I wanted any and all BIFs to be color
coded (maybe color them red for instance). Or is that a higher level?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
