if I may interject, the O.P. was asking for generic coding,
where the object method does not know its data source expression.
but in my opinion (yes it is an opinion, not doctrine)
it is better to plan well and hard-code in ORDA,
generic coding does not deliver like it does for the classic
Chris,
On Tue, Feb 4, 2020 at 12:58 PM Chris Belanger via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> // The ‘field’ that needed to be updated with the KEY of the selected
> option would be something like: //
> Form.en_edit.contact // which, say, translates to [Company]contact in
> classic 4D
>
>
Hi All,
I few months ago, I was wishing (again): why can’t a listBox have focus and
then the user just type some characters and the listbox highlights the matching
row?
You know, like so many other windows can do in programs / OS’s.
4D does not let you ‘see’ or process keystrokes when the
Hi Kirk,
I appreciate how generous you are with answering questions on this forum.
I understand the 1) 2) 3) points you make. I love the fact we can ‘attach’
things to Form. Instead of using process vars. I do not use a single process
var in my most recent projects.
I had to do a weird
Thank you for your input.
Naturally, if the object name gets to be exactly the same as the ‘expression’
that works (IFF the value is stored in Form.[whatever] )
But when the ‘expression’ is an attribute in an entity, as I described, there
is no way you can name the object like that.
I have
I believe this is related to other topic that was discussed here, namely
that you cannot get pointer to object properties. So there is no way how to
get a pointer pointing to Form.LB.Browser.en_edit.FirstName.
As you noticed, you can still manipulate such form objects with commands
that accept
Chris,
For a listbox the equivalent of 'self' is the Current Item Datasource.
Let's say that is Form.LB.currentItem in keeping with your example. (It
could be something else just as well.) This is the object that corresponds
to the listbox row generally speaking. So you could have a method that
This was annoying the first time I ran into it, but overall hasn’t really
caused any serious problems for generic programming. If you name the object
with the expression, you can use something like:
Form[Object Get name(Object current)]:=x
If you need to set properties on a form object
8 matches
Mail list logo