Keith: I agree with you on the frustration with debugging an issue when you cannot really see within the object - especially when there is an object within an object.
Just like with the great ObjectTools product one needs to build a object viewer dialog from the programmers so you can see all the objects and all the sub objects in it. Once you do that it becomes much easier to work with the objects. We use objects extensively through our shell and applications. They are great - but sometimes one needs to build tools to make these other tools even better. It can take a day or two but well worth the time for all the days of programming after that. Jody > > Several people have said that passing a 4D object as a parameter is easy to > debug. > Using 4D v15.2, I think I must be missing some new feature of 4D as I don’t > understand how you can easily trace and/or debug an object when > - only the first small part of the object is visible in the debugger? > - a Design search cannot show the methods flow that use a particular > parameter? > > I’m not for or against the idea - just trying to understand the enthusiasm > for hiding parameters. > I do understand how using an object will easily allow a large and variable > number of “variables” to be passed to the server and back for an "Execute on > server” function, and the calling/receiving methods should know what they are > handling so that shouldn’t be a problem. > But for general use, I’m trying to see an advantage… > Cheers, Keith > ********************************************************************** 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] **********************************************************************
