|
1C and 2Cthen
But if there is no budget for an option then just make it work the way it
used to. Numbered indicators are a very specific set of fields (and
thankfully a dying breed) and should be in a specific part of the outline
BUT
Sadly I think your proposed solutions may be over simplified. For example
if I am using named indicators in an Indicator Data Structure (INDDS)
I would expect to find them with the numbered indicators because that isto
what they represent. With the current proposal they would not go with the
numbered indicators but with the fields. For that matter if I redefine
numbered indicators by using a BASED DS then I’d really like them in with
the numbered ones as well but I accept that that would be a bit tricky.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Apr 8, 2016, at 3:56 PM, Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx> wrote:
Since you are the active community in support of this product, you get
usedhave the power to help me make design decisions.
I have received feedback on two issues about indicators and how they
usedto behave differently with the static outline then they do now with the
live outline.
1) Named indicators now appear under the Indictors heading when they
easierto appear under fields as just another named field with indicator type.until
People have complained and want to have only the numbered indicators
the Indicators heading.
2) Numbered indicators used to appear in numerical order which was
2to find, now they appear in the order that they occurred in the sourcepeople
(similar to all the other declarations).
I have 3 options.
A) I can change to the original behaviour with no preferences.
B) I can add a preference, but set it to the original behaviour (so
will see the product change to the original behaviour when this isindicators
released)
C) I can add a preference and set it to the current behaviour
So submit your votes to me
A vote of
1A
2A
Means named indicators will now appear under fields and numbered
will appear in numeric order - no additional preferences
A vote of
1C
2C
Means the product will behave just as it does today, but there will be
--additional preferences that will enable the old behaviourClient for System i & iSeries (WDSCI-L) mailing list
Vote away, let your voice be heard :-)
Edmund
--
This is the Rational Developer for IBM i / Websphere Development Studio
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
