This article is another Support Debugging Tool Non-Logging Trigger example and is a follow up to two previous articles:
This example stores the size and position of the SmartList window using a very similar technique to the post from earlier this week. The main difference is that instead of storing a setting in the Dex.ini file, this time it uses a Support Debugging Tool Parameter. These Parameters are stored in the SY_User_Object_Store (SY90000) table, this is the same table that Visual Basic for Applications uses for the DUOS (Dynamic User Object Store).
The reason that the code uses the DUOS table instead of the a Dex.ini setting is so that it can handle being used in a terminal server or Citrix farm environment.
Below is the reasoning:
The other big difference with this example is the enhancement to allow control of the size of the left hand (TreeView) and right hand (ListView) panes of the SmartList window. As mentioned in Mark's post, when the window is resized the size of the left pane increases to a point where it is much larger than required and is wasting a huge amount of screen real estate.
Example screenshot showing large amount of white space for left pane of Smartlist window
With this customisation, the size of the left pane can be set as a percentage of the total window size ranging from 5% to 95%. I have found that a value of 10% or 15% works well.
Example screenshot showing reduced amount of white space for left pane of Smartlist window
The example uses four Trigger IDs:
Use of the SMARTLIST_ACT trigger on the WindowActivate event was required as using the SMARTLIST_PRE on the Form Pre event was too early and the window field size changes did not take effect.
The Support Debugging Tool Debugger Settings file with these triggers is attached as an archive to the bottom of this post.
Please leave a comment if you find this example useful.
Thanks for the wonderful article... :) Smartlist pane resizing has been a topic quite some time and there are product suggestions which have been placed in Microsoft Connect. :) This is very helpful.
Posting from Jivtesh Singh at About Dynamics, Development and Life
Posting Mark Polino at DynamicAccounting.net
How do you load the xml file?
After loading the Support Debugging Tool. Goto Tools >> Support Debugging Tool and then use Options >> Configuration Export/Import to load the debugger settings xml file. Use the path button to find it and click Import.
If you want all users to have this functionality, you will need to ensure the Support Debugging Tool is set up using the Recommended Configuration as described in the User Guide PDF.
I was able to upload and implement the code, yet SmartList shortcuts are no longer working for my team (as they once were). I will need to roll this back - I'm just hoping I can! Thanks...
To disable the code, you can either mark the triggers as disabled or delete them entirely.
From the Support Debugging Tool main window, select Options >> Automatic Debugger Mode Status and use the Unregister button to unregister all Triggers.
Then select Options >> Setup Automatic Debugger Mode and click on the Administration Button. From there you can mark the triggers for deletion, mark them as disabled or set them to not start automatically.
Click OK to save the changes.
I would be interested in understanding why the shortcuts stopped working as this code should not have any side effects.
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.