485
edits
Using dfSplat to identify object leaks: Difference between revisions
Using dfSplat to identify object leaks (view source)
Revision as of 15:31, 24 March 2020
, 24 March 2020more spelling etc..
m (readability) |
m (more spelling etc..) |
||
| Line 106: | Line 106: | ||
=== Final notes === | === Final notes === | ||
* Beware that you use the Object Inspector and not the Panel Inspector as the latter one is not suitable for this task. The Object Inspector will enumerate ALL objects in your application and | * Beware that you use the Object Inspector and not the Panel Inspector as the latter one is not suitable for this task. The Object Inspector will enumerate ALL objects in your application and tests which of those objects actually exist or not. The Panel Inspector will only query the objects for the current panel and if objects are created dynamically, it won't actually show them! The Panel Inspector was created to give you much faster access to your current view or panel, but it does that at the cost of not enumerating every object (hence why it is faster) | ||
* If you want to test your code to see if it does correctly destroy all the dynamic objects it creates then it is most likely best to create a small temporary program for that. Obviously you can debug your full program, but the object inspector might be very slow to process every single object in your program on opening each time. | * If you want to test your code to see if it does correctly destroy all the dynamic objects it creates then it is most likely best to create a small temporary program for that. Obviously you can debug your full program, but the object inspector might be very slow to process every single object in your program on opening each time. | ||