× 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.



Thing is actions are defined at various levels of the product. The documentation shows the keys defined in the base LPEX editor. On top of that, though, you have various parsers with their own actions, WDSC proper and its actions, then WDSC's parsers' actions, etc. etc.

The split-view actions are defined in one of the LPEX classes that link to Eclipse. If you're really curious: ?api > Eclipse Packages > com.ibm.lpex.alef > Class Summary > LpexAbstractTextEditor.

[Yes, a (sample) command to display / print all the key bindings for the current window is on the TO-DO list somewhere...]

AGlauser@xxxxxxxxxxxx wrote:
Thanks Adrian. Not sure if it is intentional or not, but I'm not seeing either of those actions (nextView and prevView) in my documentation. If I do ?lpex, then go to "Editor commands, actions, and parameters", then "
Default editor actions", those actions do not appear in the list.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.