also for the record, this problem exists in v13.6 in windows as well as
the copy & paste solution helps.
closing and reopening the help tips window also generally clears the issue
for a while.
On Tue, Jun 12, 2018 at 7:48 AM Pat Bensky via 4D_Tech <email@example.com>
We manage help tips this way:
- For each object, select the On Mouse Enter form event
- We have a Help Tip named "HelpText" which simply contains a variable,
tHelpText. Select that Help Tip for each object.
- On the object, populate the tHelpText variable in the On Mouse Enter form
for the record, problem does not exist for v14 or later.
this is basically a compatibility issue between macOS 10.8/9 and 13.6
(evidently a regression from 13.5, really sorry about that...),
which was released in the first half of 2015.
> 2018/06/12 13:22、Dan Ivy via 4D_Tech
I wouldn't beat myself over that.
UI threads are never preemptive. (and who needs helps tips outside the UI?)
2016/11/08 6:22、Keith Goebel
Perhaps not such a good solution now, with Preemptive Processing not working
when there are IP vars
The messages in the thread "Text Editing Bug Introduced with v13.6" (from
10/2015) might shed some light on things.
Douglas von Roeder
On Mon, Jun 11, 2018 at 12:50 PM Alan Tilson via 4D_Tech <
> Hello Jim & everyone,
> I still have this
Hello Jim & everyone,
I still have this issue with 4D v13.6 in sometimes in Help Tips and
sometimes in text fields.
Has it been resolved somehow?
On Sun, Nov 6, 2016 at 7:13 PM Jim Labos - infobase
> Sorry for double post. I meant to post to 4D Tech)
> The first edit
But you can use xliff references in help tips. I have been using successfully
and for a long time the :resourceId,stringNbr notation. Actually I'm using an
IP variable, like :<>STRHelp,82
The help tip editor shows the reference, but at runtime I'm getting the correct
The usage of an IP
also useful to know about help tips:
1. they can be set by code (since v13):
2. the editor is not XLIFF compliant. the language, by contrast, supports XLIFF:
I handle Tips text the easy way - simply assign an IP text variable to each tip.
Have a method that either populates the variables or clears them - depending on
whether you want text to display in the tips.
Perhaps not such a good solution now, with Preemptive Processing not
Mail list logo