RE: Viewable Items on a Drop List in Forte V2

Question

Hi Kumar,
Let me guess, you're using windows NT 4.0 as your client.
I had the same problem a few months ago and raised the
question in this list.
My answer is as brief as it is unsatisfying:
It is a known bug for which there is no work around.
Forte 2 and NT 4.0 don't mix very well. Forte 3 works fine.
You think you found some logic behind the bug, but you
haven't. I just so happened it works this way for these
droplists in this window. Other droplists in other windows
will not follow this logic. Some won't even show the bug.
These are your choises:
Don't use NT 4.0
Switch to Forte 3
Don't use droplists
Use some tricks, like adding an empty row at the end
of the list.
Pascal Rottier
STP - MSS Support & Coordination Group
Philip Morris Europe
e-mail: [email protected]
Phone: [phone]
+++++++++++++++++++++++++++++++++++
Origin IT-services
Desktop Business Solutions Rotterdam
e-mail: [email protected]
Phone: [phone]
+++++++++++++++++++++++++++++++++++
/* My reality check bounced */
-----Original Message-----
From: Kumar Krishnasami [SMTP:[email protected]]
Sent: Friday, March 05, 1999 5:30 PM
To: [email protected]
Cc: Kumar Krishnasami
Subject: Viewable Items on a Drop List in Forte V2
I have a set of drop lists that are part of an array field which are
populated dynamically. If I set the number of viewable items to n,
and
if the drop list has m number of items in it, the number of items
that
actually appear is n-1 if the list contains more than n items( m>n)
and it is m-1 if the list contains less than n items (m<n).
For example, if I set the number of viewable items to 4 and a drop
list contains 7 items, the actual number of viewable items I see is 3
(4-1) whereas if the drop list contains 2 items, the actual number of
viewable items I see is 1 (2-1).
I searched through the archive of this list and found that this same
issue was raised before, but couldn't find any replies pertaining to
it.
Is this a "feature" of Forte V2? I tried the same thing with Forte V3
and it does work fine in V3.
Any pointers would be appreciated.
-- Kumar Krishnasami.
p.s:- It doesn't matter how I set the viewable items. I tried both
setting them through the windows workshop as well as in the code
after
the self.Open() in the Display() method. The behavior is the same in
both cases.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

On Wed, 28 Jan 1998 11:50:42 +0000, [email protected] wrote:
I have noticed that Drop List widgets show an initial value equal to
the first value in their Element List. However, this does not seem
to happen as soon as the Drop List is placed inside a grid with a
mapped type. In this case, the drop list shows a blank value
initially. Once a value is selected from the drop down list, it
always has a value.I have found the following behaviour to be true of DropLists with an
object mapped type (ie, TextData as opposed to string): If you
instantiate the mapped attribute in the Init() method (ie,
self.theDroplist = new()), then the DropList will display the first
item in the list as selected when the window comes up. If however, you
do NOT instantiate the mapped attribute, then you get the behaviour you
are observing where the DropList defaults to showing nothing until the
user makes a selection. It's kind of an odd behaviour, but you can
take advantage of it in cases where you want to force something to be
selected by the user, but you don't want an initial default.
Dale
================================================
Dale V. Georg
Systems Analyst
Indus Consultancy Services
[email protected]
================================================