![stella ithink free download stella ithink free download](https://images-na.ssl-images-amazon.com/images/I/41w9u0ZAxhL._SX258_BO1,204,203,200_.jpg)
the thing that really annoys me about these runtime errors is the time spent battling thinking you must be implementing it wrong. Would have been nice to have model api to use to test what is an application model and what is a shipped model but this was the best way round.ĬharlesWilt wrote:Was wondering if you're considering adding an export/display changed only.Tried to do this for you this morning as it is a good enhancement BUT again the old runtime fails me again. You may have several plex.ini files on the go and each one has to have these setting in. I mentioned a potential problem which you are not suffering from but thought i would post it here. I could not think of any other good way of determining which a sites group model names were, no model api avaliable to do this, and the plex ini file recorded the group models so why not use this. The ini file is then read for GMFile settings under Options as this records application models, File settings records your locals which could have any name you choose which is no use when interogating plex objects. The directory can be anything, when the model api client loads up in this case it checks the current plex.exe being run and gets its location then gets it's INI file from the same directory (potential problem). GMFile1=C:\mydirectorytogrpmdl\mygroupmodelnamewithnoextension
![stella ithink free download stella ithink free download](https://arc-anglerfish-washpost-prod-washpost.s3.amazonaws.com/public/AKYVPCVJZYI6XPFFASFSOWNERE.jpg)
See attached from Help file, under "Instructions" for Search Large Property hope something is of use.Īll working as coded phew. Give help a quick read and it should give you some ideas. Two weeks ago a developer had a problem with particular panel that was exhibiting 'funny' runtime problems, I viewed the large property of the panel using the Display Large Property tool and saw pretty quickly some of the controls had fix right settings under the expanded state which was causing problems which is harder to spot when looking at the settings of a control in plex ide We use a version of Object Browser+ most days during maintenace or development as we select the objects we are changing in plex and record them via the model api to our changement managment objects record. The next release cycle we are going live with a few new webservices that used to be implmented as 3rd party dll and natively written rpg, we aim to clean installtion directorys and libraries up of obsolete objects Impelmented Programs Tonight we go LIVE with one of our 3 releases a year so it so happens am also using Export Large Properties to take a snap shot of ALL large properties in our application models for changement and impact analysis during the next release cycle. Down load help file and under each tool there is an overview section where I detail how I use them.ĭuring developement I use Search Large Properties multiple times a day especially to find messages and how I and others wrote bit of source code, today needed to seach for anywhere in the models (application and libraries) for Base64