[NOT Solved] v13 - Konstant problem

Sorry Jody, I thought that renaming the constants solved the issue. It did not... I thought maybe the issue was the xlif file damaged in same manner, so I recreated the file from scratch (using 4Dpop), with no copy paste. I also recreated, no copy paste, the previously posted method wrapping Set

Re: [Solved] v13 - Konstant problem

Chip: Hate those kinds of things. Hours to learn, it seems like hours wasted. Thanks for letting us know the solution. Jody > On Jun 26, 2018, at 7:37 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Koen > Thanks > > While you were not exactly on track it did point me in t

[Solved] v13 - Konstant problem

Koen Thanks While you were not exactly on track it did point me in the right direction. It seems that at least the following 2 values "step" on something internal to 4D Listing_Menu Main_Menu By reversing the naming convention to Menu_Listing Menu_Main The Konstants now correctly function. C

Re: v13 - Konstant problem

Hi Chip, Just a wild guess, you don't have by accident a field or method with the same name? Is your constant correctly styled in the method editor? Is your constant typed as longint in 4D Pop? Or as auto? HTH Koen > Op 26 jun. 2018, om 00:14 heeft Chip Scheide via 4D_Tech > <4d_tech@lists.4d.

v13 - Konstant problem

I have been using 4DPOP constants editor to create Konstants for my system. One set of Konstants is: Main_Menu : 1 : Listing_Menu : 2 Entry_Menu : 3 Edit_Only_Menu : 4 in my start up code I have this line of code utl_menu_Set_Menu_Bar (Listing_Menu) The Konstant tokenizes, and in the debugger