As a follow on to the article: Using Support Debugging Tool Non-Logging Triggers, I thought I would post a few small examples of how Non-Logging Triggers can be used for simple customizations.
There have been some other examples posted in the past on this and other blogs. If you are interested have a look at this post: Using the Support Debugging Tool with Real Life Examples.
This example demonstrates how to allow any window to remember its size and position. For this sample, I used the Purchase Order Entry window.
The method is in this example is the based on how the Support Debugging Tool itself keeps track of its own windows size and position and stores the data as a single line in the Dex.ini file. For example:
Note: The position information is relative to the Microsoft Dynamics GP main application window and so can show negative figures when the window was last positioned higher than or left of the main window.
The example uses two Trigger IDs:
The Support Debugging Tool Debugger Settings file with these triggers is attached as an archive to the bottom of this post.
For some related window size and position posts, see the following articles:
21-Aug-2012: See the updated version of the code at Update: Adding Window Size and Position Memory using the Support Debugging Tool. This update uses a table rather than the Dex.ini to store the settings.
Posting by Jivtesh Singh at About Dynamics, Development and Life
Posting from Mark Polino at DynamicAccounting.net
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.