Typing ui objects?
Bill Weale (6/6/14 8:43AM)
Bill Weale (6/6/14 12:44PM)
Jeremy Roussak (6/6/14 2:02PM)
Bill Weale (6/6/14 2:04PM)
Jeremy Roussak (6/6/14 5:45PM)
Joshua Fletcher (6/6/14 6:36PM)
Manila (6/10/14 9:30AM)
Manila (6/11/14 4:21AM)
Bill Weale (6/6/14 8:43 AM)
Is there any point in coding compiler declarations for objects such as
popups/dropdowns, listboxes, tab controls, etc?
(I'm trying to recall if any of these can assume more than 1 type, so
that removing ambiguity would be a great reason, but I can't think of
one.)
Bill
William W. Weale, III
Business Owners Support, LLC.
Operations Analysis
MIS Advising
Decision Support Systems
Bill Weale (6/6/14 12:44 PM)
Man, I just can't believe the number of languages I have to keep up
with!
8-)
On Jun 6, 2014, at 12:36 PM, Joshua Fletcher wrote:
color><param>00000,0000,DDEE/param>QQFT
/color>
Jeremy Roussak (6/6/14 2:02 PM)
I'm not sure about the others, but my experience is that tab controls
don't work compiled unless they're typed.
Jeremy
Jeremy Roussak
jbr@...
On 6 Jun 2014, at 13:43, Bill Weale <bill.weale@... wrote:
color><param>00000,0000,DDEE/param>IIs there any point in coding
compiler declarations for objects such as popups/dropdowns, listboxes,
tab controls, etc?
(I'm trying to recall if any of these can assume more than 1 type, so
that removing ambiguity would be a great reason, but I can't think of
one.)
Bill
/color>
Bill Weale (6/6/14 2:04 PM)
I agree that what you suggest is necessary; it's the fact that it's
necessary that is my complaint.
Think about it. What do you have to charge for your time? Maybe I do
become glassy-eyed-numb before most, but it is 2014.
We have a Compiler window in which we can trigger 4D to do its
thing--a lot of things in order to compile. To get there we've had to
use the method editor (me event= on begin coding/on end coding) and
we've had to use the form editor (fe event = on begin forming/on end
forming), etc.
Tell me there's not a group of features in 4D that couldn't have been
dropped altogether or that could be delayed a bit so that there
were/are some resources for an engineer to run selected
compiler/compiling functions while we're coding and forming so that,
where needed (or when/where the developer chooses) ambiguities are
presented so they can be tended to. After that, all variables *are*
typed.
Simplistic? It should be. Just think where 4D could be now if its
learning code flattened out just a bit *before* the end of a
developer's life span...
--Bill
(Offered, of course, with my usual level of restraint.)
On Jun 6, 2014, at 12:10 PM, Kirk Brooks wrote:
color><param>00000,0000,DDEE/param>AAs part of good compiler hygiene
compile with the
"All variables are typed" option. If you haven't been doing this the
first
time through you may feel dismayed at the number of declarations you
need
to go back and do - including any of these form objects you've ignored
so
far. In my experience the time has been worthwhile.
/color>
Jeremy Roussak (6/6/14 5:45 PM)
On 6 Jun 2014, at 17:36, Joshua Fletcher <JFletcher@... wrote:
color><param>00000,0000,DDEE/param>------Original Message-----
/color><color><param>8826F,0000,8219/param>AAlso, I find it much
easier to let 4D manage most of those objects (tabs
excluded). Just delete the variable name in the Property List. This is
especially helpful on list box headers and footers. If you don't need
to
address them directly let 4D manage the scutt work.
/color><color><param>00000,0000,DDEE/param>
QFT
/color>
QFT?
color><param>00000,0000,DDEE/param>
I recently found out that this is a "thing". If you remove the
variable name you don't need the typing definition, 4D creates the
variable on the fly.
Of course this does not work if you actually needed access to the
variable. Use this technique for situations where you'll never need to
access that form object via the variable.
/color>
Even that's not quite right, Josh: you can use the variable by OBJECT
Get pointer(Object named; ...)->. It's a bit tedious, though.
Jeremy
Jeremy Roussak
jbr@...
Joshua Fletcher (6/6/14 6:36 PM)
color><param>00000,0000,DDEE/param>
/color>
-----Original Message-----
color><param>00000,0000,DDEE/param>AAlso, I find it much easier to let
4D manage most of those objects (tabs
excluded). Just delete the variable name in the Property List. This is
especially helpful on list box headers and footers. If you don't need
to
address them directly let 4D manage the scutt work.
/color>
QFT
I recently found out that this is a "thing". If you remove the
variable name you don't need the typing definition, 4D creates the
variable on the fly.
Of course this does not work if you actually needed access to the
variable. Use this technique for situations where you'll never need to
access that form object via the variable. Remember you can still use
the Object name for any of the OBJECT methods.
Kind regards,
Josh
--
Josh Fletcher
Technical Account Manager
4D, Inc
Manila (6/10/14 9:30 AM)
Josh,
I have found that I still need to set the type of the variable in the
form definition if I want it to act like a variable of a certain type.
For example, a form object with no variable name and no language
declaration that will be a date should be set as "Date" in the form
editor; otherwise, you don't get all the default behaviors of dates.
The same is true for numbers.
Walt Nelson (Manila)
Joshua Fletcher
color><param>8826F,0000,8219/param>AAlso, I find it much easier to let
4D manage most of those objects
(tabs excluded). Just delete the variable name in the Property List.
This is especially helpful on list box headers and footers. If you
don't need to address them directly let 4D manage the scutt work.
/color><color><param>00000,0000,DDEE/param>
QFT
I recently found out that this is a "thing". If you remove the variable
name you don't need the typing definition, 4D creates the variable on
the fly.
Of course this does not work if you actually needed access to the
variable. Use this technique for situations where you'll never need to
access that form object via the variable. Remember you can still use
the Object name for any of the OBJECT methods.
/color>
Manila (6/11/14 4:21 AM)
Bill,
I have several form objects in v14 (in 4DAPPBUILDER PRO), and they all
"remember" what type they are. Numeric form objects know that they are
numeric, so they accept numerical values and they allow numerical
display
formats. I just re-opened one of the forms and looked at the
properties of
one of the objects, and the type is still set to "numeric."
Walt Nelson (Manila)
Bill Weale said:
color><param>00000,0000,DDEE/param>II've always tried to remember to
set these, but for the longest time it
was not obvious that 4D was "remembering" them. This goes back for
years.
Minutes or weeks after I had last worked on a form, I would reopen it
and a form object which had a variable name property would show pretty
much any type at random, regardless of the object type or what I had
set it to in the Property List. And this included form variables which
I was religious about typing in code.
--Bill
/color>
Reply to this message
Summary created 6/11/14 at 8:03AM by Intellex Corporation
Comments welcome at: feedback@intellexcorp.com