Jump to content

Emilito

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Emilito

  1. Hallo @Joel Bodenmann,

    Thanks for the quick answer... Now I am looking for a replacement font in https://fonts.google.com/ that looks similar to Arial. There most of them have Apache licence and there should be no problem.

    When I refered to licence terms for embedded devices I meant if the font could be used(just the graphical art, because the ttf file propably will not be used) in embedded devices like a car control system, radio, etc... In this link it states different licences depending on the usage.

    https://www.myfonts.com/fonts/microsoft/arial/licensing.html

    For example it says that for printed documents there is no restriction, but if you wanna use it in a server or in an Android app you have to pay for the use.

  2. Hallo,

    I have a question regarding fonts. I wanted to use the Arial font, but someone pointed it out that this font is property of Microsoft and that its use is restricted to the licence that everybody has within its PC. I never thought about it and now that the product that I am developing is going to be sold I am little bit confused about it.

    Could anyone share their experiences regarding font use in embedded devices, and more specifically the use of Arial within a device that has not a Microsoft OS. Am I a little over the top or is it allowed to use any font without care and without having any problems?

    I found this link about Arial licencing, but does does not say anything about using it in embedded devices. https://www.myfonts.com/fonts/microsoft/arial/licensing.html

    Can I use all the fonts included in demos/modules/gdisp/fonts/?

    Regards, Emilio

  3. On 8/24/2016 at 11:59, Joel Bodenmann said:

    Hi,

    I created a new topic out of your post because it was unrelated to the Kinetis Design Studio.

    The GDISP_DRIVER_VMT macro is only used internally. That's why there is no documentation of it. It's a macro that gets defined by the driver itself. Unless you are writing your own driver you don't have to worry about it. Just include the driver(s) that you want to use and everything else should be taken care of.

    Just to clarify. If you are going to add you own display driver, then you should define the GDISP_DRIVER_VMT macro. I added my own display driver so in my case the source file gdisp_lld_XXX.c is like:

    -----------------------------------------------------------------

    #include "gfx.h"

    #if GFX_USE_GDISP

    // Define that we are going to compile our own display dirver
    #define GDISP_DRIVER_VMT      GDISPVMT_YOURDRIVER

    #include "gdisp_lld_config.h"

    // I changed the location of the display driver source file
    #include "src/gdisp/gdisp_driver.h"

    #include "your_board.h"
    #include "OtherFilesForYourHardware.h"

    -----------------------------------------------------------------

×
×
  • Create New...