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



I've found that the only way I can get user key actions to do anything
is when I check the box to Disable Parsing (in the main LPEX Editor
panel under preferences). Seems that I shouldn't have to do this though,
you would think that the user should be able to customize their keyboard
whether parsing is set on or off (and I need to keep it on, I loose a
whole bunch of features when parsing is disabled).

When I am able to get newline to work on my enter key (again, with
parsing disabled), it doesn't go to the leftmost position of the prefix
area. It only goes to the leftmost position of the non-prefix (edit)
area. The goal was to get my cursor to the area where I can enter a
prefix command, using a single keystroke. Seems like at this point, I
would need to somehow create a keyboard macro that does both Newline and
PrefixHome, but I don't know how to set this up in RDi.

Anyone out there have a solution for this?





+++ This email and related attachments may contain confidential information intended exclusively for the addressee. Unauthorized use, disclosure or distribution of this material is prohibited. If you received this message in error, please advise the sender and delete all copies of it. Content is provided by the individual sender and does not necessarily reflect the views of the Company. Though sender believes this transmission to be virus-free, it is the recipient's responsibility to ensure that it is.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.