Thank you all for your suggestions, the flag came to mind, too. That's a feasible way to go.
Our current solution was to not act until form unload which is in our use case OK as we just store the status of the listbox. Still I'm not really happy about this change because one way or another you have to touch many places in the code if you didn't handle the event completely generically. Regards, Tilman > Am 08.02.2017 um 21:42 schrieb Chuck Miller <[email protected]>: > > Yeh what we used to do was to set a boolean to false and then when code runs > set to true. Only run code if boolean is false. We had the same type of > problems in really old versions of ALP > > Regards > > Chuck > ------------------------------------------------------------------------------------------------ > Chuck Miller Voice: (617) 739-0306 > Informed Solutions, Inc. Fax: (617) 232-1064 > mailto:cjmiller<AT SIGN>informed-solutions.com > Brookline, MA 02446 USA Registered 4D Developer > Providers of 4D and Sybase connectivity > http://www.informed-solutions.com > ------------------------------------------------------------------------------------------------ > This message and any attached documents contain information which may be > confidential, subject to privilege or exempt from disclosure under applicable > law. These materials are intended only for the use of the intended > recipient. If you are not the intended recipient of this transmission, you > are hereby notified that any distribution, disclosure, printing, copying, > storage, modification or the taking of any action in reliance upon this > transmission is strictly prohibited. Delivery of this message to any person > other than the intended recipient shall not compromise or waive such > confidentiality, privilege or exemption from disclosure as to this > communication. > >> On Feb 8, 2017, at 3:04 PM, Tilman Haerdle <[email protected]> >> wrote: >> >> With 4D v16.0 the event "On Column Resize" fires live during resize of >> listbox columns. >> >> This has severe effects on methods who do stuff after resizing a column. If >> the method takes to long irt is invoked again while it is still running >> which results sooner or later in a stack overflow and subsequently a crash. >> >> I'd wish there was a "On After Column Resize" event for methods who take >> place after the fact and not during the resize action. >> >> Any strategies to cope with the current implementation in v16? > > ********************************************************************** > 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] > ********************************************************************** ********************************************************************** 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] **********************************************************************
