Developing for Dynamics GP

by David Musgrave (Perth, WA, Australia) and the Microsoft Dynamics GP Developer Support Team (Fargo, ND, USA)
Search Form
  • Advanced search options...
Options
Tags
News

Dates of Interest

11-Jul-2008: Blog Created by David Musgrave.
03-Oct-2008: Syndicated to the Dynamics Communities.
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.
20-Nov-2009: First Post by Alice Newsam.
21-Apr-2010: First Post by Allan Cahill.
19-May-2010: First Post by Marian Verzosa.
24-May-2010: Blog Migrated to new Platform.
28-May-2010: Created Facebook account with blog feed.
15-Aug-2011: First Post by Development team.
05-Sep-2011: Created http://aka.ms/Dev4DynGP and http://aka.ms/SDT Shortened URLs.

Social Networking & Syndication

Follow David Musgrave and the blog on:

Developing for Dynamics GP on Twitter

David Musgrave on LinkedIn

Developing for Dynamics GP on Facebook

This blog at Dynamics Communities

Shortened URLs

This Blog: http://aka.ms/Dev4DynGP
SDT Portal: http://aka.ms/SDT
Menus for VST: http://aka.ms/MVST

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.
WorldMaps
WorldMaps Statistics since 24-Feb-2009:



Click for WorldMaps Stumbler
Translator Tool
Links
Contents
Newsgroups & Forums Links
Blog Links
Resources Links
Favourite Posts
Archives
Archives

Any Font in the Dexterity Script Editor

MSDN Blogs > Developing for Dynamics GP > Any Font in the Dexterity Script Editor

Any Font in the Dexterity Script Editor

5 Jul 2009 8:00 PM
  • Comments 2

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

, , , , ,
Comments
  • Vaidy Mohan
    6 Jul 2009 4:13 AM

    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

  • 7 Jul 2009 1:21 AM

    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

Page 1 of 1 (2 items)
Comments Information

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.

Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post