On Sep 17, 2016, at 2:00 PM, Peter Jakobssonwrote: > This is a phenomenon I (we ?) have lived with for a couple of centuries and > just thought I’d bring it up for discussion since the new OBJECT SET ENABLED > command seems to inherit the old behaviour. > > Lets say you have a text array process variable manifesting as a pop-up menu > on one form and you disable it on that form. > > If you then open a different form which uses that same variable in a pop-up > menu, it remains disabled there as well. 4D never seems to reset the enabled > state to some default. What this means is that I always have to explicitly > set pop-up menus to “enabled” in the On Load phase, even though there may be > no state management required in a particular form. > > What do other people do to address this ? (Or am I missing something in front > of my nose).
You have discovered the secret reason why using object names is preferred over using variable names. Setting a object property based on a variable name can allow it to persist after a form is displayed because the process variables continue to exist. Using object names guarantees that will not happen. Yeah… I know. Now that you think about it, it makes sense :) Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
