Well, this is what it turned out to be. I had fixed a bunch of these places but
I missed a small handful. I didn't report the issue either since it was such a
simple little fix, but other developers converting to v17 should definitely be
aware of this one.
Thanks all,
Jeff
> On Aug 14, 2018,
I first ran across this with v16R6, but in conversations with other
developers, not everyone was running into the same issue, so I didn't
report it as a bug (or take the time to isolate and repeat). In my
case, the commands were being called from a component (Foundation
v5.7).
Good luck,
dave
Thanks for the tip - I ran across this too and had already changed all of
those. I'm going to double-check though.
> On Aug 14, 2018, at 11:53 AM, Dave Nasralla via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Yes I have seen this. The first thing I would look at is the command:
> SET MENU
Yes I have seen this. The first thing I would look at is the command:
SET MENU ITEM PROPERTY(<>Fnd_Menu_FileMenu_t;-1;Associated standard
action;ak quit)
The old constants need to be updated to the new ones (eg. ak quit) . I
found if I "touched" a method with the old constants, they no longer
What we are seeing is a lot more obvious - in the application mode the Copy
menu item just becomes permanently disabled after awhile.
We haven't found a pattern yet - it could well be something in our own code —
but we haven’t changed our menu handling code in a long time.
> On Aug 9, 2018,
I just had an instance (v17 Mac) where "command C" and "command V" to copy and
paste some form objects between two forms had no effect. It worked when I used
the menus with the mouse. That also seems to have cured the problem. This
happens on such rare occasions that I've been blaming my
Is anyone else experiencing a problem in 4D v17 on Mac where the Copy menu item
in the Edit menu becomes disabled permanently until a restart of 4D?
**
4D Internet Users Group (4D iNUG)
Archive:
7 matches
Mail list logo
