On Sat, Feb 25, 2017 at 1:33 PM, Jeffrey Kain via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Menu bar editor is for baby programmers...
>
On behalf of baby programmers everywhere, let me say "Wh"
**
4D Internet Users Group (4D
Menu bar editor is for baby programmers...
:)
> On Feb 24, 2017, at 7:27 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Welcome to the world of the 4D Menu Editor. It works, but it has problems. It
> is not the most robust editor window in the 4D Design environment. Same
>
On Feb 24, 2017, at 2:00 PM, David Adams wrote:
> I just tried it today in a structure built from the ground up in V16. On
> Mac. The menu editor is buggy to the point of nearly unusable.
>
> Has anyone been using the V16 version of this tool without trouble? Or,
> contrarily, are there already
> Does anyone know, is there an actual 'vote' mechanism, or are you just
> supposed to put down a +1 post?
This tech tip should help explain the difference between +1 and voting:
Tech Tip: How to vote for a feature request
http://kb.4d.com/assetid=76726
-Tim
I recently tried to make a jump from v13 to v16 but abandoned the effort and
went with v15.4. I ran into several issues that work without problems in
v15.4. Some menu issues was one of the problems (ie. when calling edit
users I would end up with the design menus and when my window management
Yes! And let's not overlook the ever popular series of process arrays named
aTemp1, aTemp2, aTemp3 ... even better because they are referenced by
pointers referring to some other pointer initialized - someplace.
(Deep breath)
Ok, thanks for that moment.
On Fri, Feb 24, 2017 at 12:12 AM, Herr
I hate working on other developer's code where I am expected to guess the
type by its use and context. It is a waste of my time and therefore a waste
of my client's money.
It is often possible to correct/optimise code without understanding the
context. I was a photographer in a previous life, and
> Am I insane because I start by search/replace variable names prior
> to understand some code from another?
If you're insane, I'm insane with you. I can't really "read" code. Maybe
some people can. I can read methods, but visualizing how they fit together
and work? That's harder. I like to dig
> Le 24 févr. 2017 à 09:12, Herr Alexander Heintz via 4D_Tech
> <4d_tech@lists.4d.com> a écrit :
>
> [...]
> Concerning the descriptor, I have found it more useful to have that up front,
> spearated by underscore:
>
> $t_myText
> $al_myLongArray
> o_processObject
>
> etc.
> Why?
> 3 reasons:
quite interesting read, thanks.
The value of sensible naming never shows more strongly when you have to work
with OPC (Other Peoples Code) and find generic variables like S_1 or AR1 that
are used in changing roles throughout the code and are an incredible pain to
debug, or even replace…
10 matches
Mail list logo
