What I find most annoying is that this real-time update of the outline view DOES work when editing a DDS source.

And when doing java editing.

What's the difference? It's the exact same editor.

I'm trying to get more users here on WDSCi (7.0), but so far only 1 jumped on the wagon...

Peter Colpaert
Software Engineer, Philips Consumer Luminaires

Industrieterrein Satenrozen 11, 2550 Kontich, Belgium
Tel. +32/ 3 450 74 09, Fax +32/ 3 450 74 33, Internal 1317
peter.colpaert@xxxxxxxxxxx, www.philips.com

Simply Switch to printing double-sided and printing less

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-
bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: maandag 24 augustus 2009 18:46
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] justifying RDi when WDSCi 'still works'


We don't have the most common things the .NET people have enjoyed for
years. How about function completion, for instance? Ctrl+Space. All
see on V7.0 is (char(50), char(3), char(20), int) and so on. No
description of what the parameters are, even when the function is
defined in the source I'm working on. How about real-time update of
outline view since it becomes obsolete the moment I insert so much as a
blank line?


The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].