> The form was set in v14 to have an active menu bar, called “Main”. The
> component doesn’t have a menu bar “Main” but each parent application does.
I am surprised that this even worked.
the documentation is quite clear that menu bars created vis the Tool Box Menu
Editor are not shared,
so
It is always frustrating to spend days tracking down a bug and finding out that
it is a fundamental 4D bug. I spent a week earlier this year tracking down a
significant bug with OB SET that was as reported with v16 R2 but as far as I
can tell has not been fixed (ACI0096772).
Now a significant
> Le 17 déc. 2017 à 20:01, Jeremy Roussak via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> I’m changing from v14 to v16 and am getting confused.
>
> I have a component which is used in two applications. It displays and works
> with a multi-page form which is entirely self-contained. The
I’m changing from v14 to v16 and am getting confused.
I have a component which is used in two applications. It displays and works
with a multi-page form which is entirely self-contained. The form was set in
v14 to have an active menu bar, called “Main”. The component doesn’t have a
menu bar
The next meeting of the Montreal 4D Club will be held Wednesday December 20th
at 7 PM.
The schedule for the next meeting is as follows:
News
Questions
Presentations
- Open meeting. Bring your Xmas questions and presentations.
End of the meeting
We usually end up at some sort of restaurant after
5 matches
Mail list logo