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



Hi Sam,

It seems that you have picked a key binding which is reserved by the
debugger (Ctrl+Shift+I is for Inspect in the debugger).
You could try and fiddle with the preferences (Windows>Preferences,
General>Keys) and try to only have the key binding apply to debug views,
but then the key would not be available when LPEX is the editor used during
debug.
I would recommend that you choose a different key (ie Ctrl+I) instead.

thanks,

Violaine Batthish
eSupport Champion
WebSphere Development Studio Client
IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 05/21/2007 03:15:07 PM:

WDSc Version: 7.0.0
Build id: 20070202_0030
LPEX 3.2.2 (build 9-Jan-2007)

I'm trying to set Ctrl-Shift-i to find whatever I have selected, just
like I
had in version 6.

In Preferences/LPEX Editor/Find I have checked "Select Found Text".

In Preferences/LPEX Editor/User Key Actions I have set c-s-i Action to
findSelection.

In the LPEX editor, if I highlight some text and key "action
findSelection"
the find works and the found text remains highlighted.

But when I highlight text and press c-s-i I get an error dialog "Error
Evaluating" with a message "A stack frame must be selected to provide a
context for evaluation."

What am I doing wrong?

Sam


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.