Results for "Author: cody rutkowski"
A different kind of INI because I don't like the ini's that are so easy to use!
A different kind of INI because I don't like the ini's that are so easy to use!
A different kind of INI because I don't like the ini's that are so easy to use!
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
When using the chameleon button user control I noticed that eventually the application will begin to run out of resources. I was extremely curious to what was causing it, and decided to identify the problem. Using the vbAccelerator GUI Resource Tracer (www.vbaccelerator.com), I was able to find the cause of the problem. In the procedure DrawFrame(...) the memory leak occurs. I implemented DeleteObject calls for the hPen and hObject. Originally the code would only call DeleteObject on the value of hObject and not hPen. Hope anyone that uses the chameleon button user control finds this helpful. This user control is hosted on this website incase you are unfamiliar with it.
Class written to create an object-orientated programming approach to array handling. Supplies nice re-usable methods that can help keep programs clean and free from common programming errors when working with VB6 arrays. Contains good formatting as well as comments. Hopefully easy to understand for anyone regardless of vb6 skills. Happy Coding, Cody Rutkowski
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use!
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
This Code Takes a script file and interprets the strings, making it do stuff, like a real vb application
A different kind of INI because I don't like the ini's that are so easy to use! example: @ Header1, Value1 @ Header2, Value2 @ Header3, Value3 @ Header4, Value4
When using the chameleon button user control I noticed that eventually the application will begin to run out of resources. I was extremely curious to what was causing it, and decided to identify the problem. Using the vbAccelerator GUI Resource Tracer (www.vbaccelerator.com), I was able to find the cause of the problem. In the procedure DrawFrame(...) the memory leak occurs. I implemented DeleteObject calls for the hPen and hObject. Originally the code would only call DeleteObject on the value of hObject and not hPen. Hope anyone that uses the chameleon button user control finds this helpful. This user control is hosted on this website incase you are unfamiliar with it.