× 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 Joe,

This is a good suggestion.  I have added it to our list of requirements.
(Boy you guys sure are keeping me busy :-) )

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab




wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/19/2006 08:38:16 AM:

In the LPEX editor, I'd really a preference that would make the "word
left"
and "word right" (Ctrl-LeftArrow and Ctrl-RightArrow, shifted and
unshifted)
stop at punctuation.  Right now it only stops at white space and that's a
pain for:

  OrderArray(oIndex).AddressLine(x) = %subst(LongAddress:curIndex:30);

You basically have to go one space at a time to get to oIndex.  The only
way
to be able to cleanly cursor around is to use what I fondly refer to as
"KlementCode":

  OrderArray( oIndex).AddressLine( x) = %subst( LongAddress: curIndex:
30);

Note the strategic spacing.  And even that isn't very helpful for dot
syntax.  So a couple of options would be nice: word cursor jumps TO the
next
punctuation mark and, word cursor jumps OVER the next punctuation mark
(the
the next position).

You might even consider (although this would be low priority) an option
to
check CamelCase when jumping, like the Java editor does now.  Include in
the
stop list not only punctuation, but a change from lower case to upper
case.
This is primarily useful to those of use who use CamelCase to name our
variables.  However, this one is probably not nearly as useful as the
punctuation breaks!

Joe




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.