Microsoft Dynamics GP Developing for Dynamics GP
A blog dedicated to the Microsoft Dynamics GP Developer & Consultant community
 
Welcome to MSDN Blogs Sign in | Join | Help

Developing for Dynamics GP

by David Musgrave (Australia) and the Microsoft Dynamics GP Developer Support Team (USA)

News

  • Please use the Blog Feedback? - Contact Us link at the top of the page to email questions relating to the blog itself.

    If you wish to ask a technical question, please use the links below to ask on the Newsgroups. If you ask on the Newsgroups, others in the community can respond and the answers are available for everyone in the future.

    Please do not use comments on pages and posts to ask questions unrelated to the topic on that page or post.



    Dates of Interest:

    11-Jul-2008: Blog Created by David Musgrave.
    10-Oct-2008: First Post by Scott Stephenson.
    04-Nov-2008: First Post by Dave Dusek.
    11-Nov-2008: First Post by Beth Gardner.
    28-Nov-2008: First Post by Chris Roehrich.
    30-Dec-2008: First Post by Patrick Roth.
    24-Feb-2009: First Post by Greg Willson.
    22-Apr-2009: First Post by David Clauson.
    04-May-2009: First Post by Ryan Wigestrand.
    19-Jun-2009: First Post by Dawn Langlie.
    03-Jul-2009: First Post by Emily Halvorson.
    23-Sep-2009: Created Twitter account with blog feed.



    WorldMaps Statistics since
    24-Feb-2009:




    Click for WorldMaps Stumbler



    Translator Tool:




    Social Networking

    Follow David Musgrave and the blog on:

    David Musgrave on Twitter

    David Musgrave on LinkedIn


    Disclaimer

    This blog is provided "AS IS" with no warranties, and confers no rights.

    The links in this blog may lead to third-party Web sites. Microsoft provides third-party resources to help you find customer service and/or technical support resources. Information at these sites may change without notice. Microsoft is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

Contents

Favourite Posts

Blog Links

Newsgroups Links

Resources Links

Any Font in the Dexterity Script Editor

Patrick Roth

Aren't secrets fun?  And while having a secret is fun in and of itself, it is also fun to share them from time to time (and allowed to share them).

The secret today is an undocumented feature that I believe was added to 10.0 SP2.  As an undocumented feature, this means:

  • It might not work for you
  • It might cause "issues"
  • Don't ask support about it if it causes "issues"
  • Might not work in the future

That said:

  • I can't see why it wouldn't work
  • I don't see what issues it would cause and is completely reversible
In the Dexterity Options window under the sanScript tab, there are currently 4 choices for fonts.  Courier, Helvetica, Times, System.
 
The font setting is hooked to the Dex.ini switch - ScriptEditorFontName.
 
The "secret" is; if you enter your own font name here Dexterity will use that font in the Dexterity Script Editor (or Script Debugger) window.
 
There is also an undocumented (as far as I can find) Dex.ini switch to change the style of the font - ScriptEditorFontStyle.  This switch allows you to set the Bold, Underline, or Italic setting of the font as well.  You can use these settings either individually or multiple settings.
 
Below, I have modified my Dexterity Dex.ini to change the font from the default "Courier" to "Verdana" by changing the ScriptEditorFontName setting.  I then also made the font style to be Bold, Italic, and Underline by adding the ScriptEditorFontStyle setting. 
 
Dex.ini Example

I'm pretty sure that this is NOT the combination I'd pick to work with but you can clearly see in the screenshot that it does work. 

Screenshot of my Dexterity Script Editor window using the above settings

Dexterity Script Editor with Font Change

One important thing to note.  While the Script Editor window will respect the settings for the ScriptEditorFontName and use that font, the Dexterity Options window DOES NOT know about the change.  If it finds a font in the Dex.ini it doesn't know about, it will switch your Dex.ini to use the default Courier font.  So if you need to go into the Options window you'll probably have to change your Dex.ini again to reflect the font you'd like to use.  This is the price of using this particular undocumented feature.

Patrick

Posted: Monday, July 06, 2009 9:00 AM by Patrick Roth [MSFT]

Comments

Vaidy Mohan said:

That's cool. I can now use my fav. font Tahoma.

I also feel like we don't normally use Options window more often, unless we change our Source Code Control frequently (which is very important settings in the Options panel) and probably some other options.

Certainly a cool feature.

Vaidy

# July 6, 2009 4:13 AM

David Musgrave said:

Hi Vaidy

I use a separate Dex.ini file for each of my development projects and pass that as a parameter along with the development dictionary in the shortcut icon I use to launch Dexterity for that project.

This is discussed in the Knowledge Base article I wrote:

How to set up the development environment when you use Dexterity in Microsoft Dynamics GP (KB 949622)

https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;en-us;949622

David

# July 7, 2009 1:21 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker