Jump to content

Joel Bodenmann

Administrators
  • Posts

    2,656
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Joel Bodenmann

  1. Hello and welcome to the µGFX community!

    Those fonts (and the two UI fonts) have been custom designed by the µGFX developers. The sources of these fonts are not openly available and therefore there won't be any easy solution for you to modify them.

    If you're a commercial customer you can contact us via e-mail to further discuss possible solutions.

  2. Just before we dive too much into this: Can you replicate the same issue with the latest version of the µGFX library?
    The font stuff (especially wrapping and alignment/justification) has been reworked intensively in a release after 2.4 (can't remember, was 2.7 or 2.8 I think - check the changelogs).

    If you integrated µGFX properly into your project you should be able to just replace the library directory.
    If upgrading is for some reason not an option, I'd recommend you to first investigate and re-evaluate why that is not an option and if the situation stays the same you can go through the changelogs and git history to figure out which patches were applied to this and cherry-pick those patches to your copy of µGFX 2.4.

  3. Thank you for your suggestion.

    If you feel like opening an µGFX channel please feel free to do so. We're happy to promote it here and on our website - I'd also join in personally.
    However, we're not going to do / maintain this ourselves. We have done this in the past (eg. the #ugfx channel on freenode) but we mainly stopped doing that as we prefer to invest our time into development.

  4. Hi,

    The font converter engine supports TTF and BDF font files. I think the font converter should reject other files but maybe that's not the case and it can't process at some point. The online font converter definitely checks for the proper file extension.

  5. Make sure that all your DMA stuff is setup properly (i.e that there are no conflicts).
    Keep in mind that the DMA stuff is not part of µGFX - it's part of the application. You need to configure all the DMA components in a way that it works for the entire application.

    You might also find this forum post helpful: 

     

  6. What exactly is "1mg" or "1Mg"?

    If you also need OpAmps you might want to have a look at the "PSoC" series of Cypress. The PSoC 4, 5 and 6 all feature Cortex-M cores. Those devices come with your regular amount of peripherals (SPI, I2C, ...) but also feature programmable analog components such as OpAmps, comparators and so on.

    There's a guide on how to use µGFX with the PSoC creator studio (their IDE) in our wiki.

  7. Hello and welcome to the µGFX community!

    The answer to all your questions is: Yes.

    µGFX has been written to run on virtually any system/platform. The STM32F103 is very well supported. In fact, when I started writing µGFX the initial development took place on an STM32F103RB6T.
    However, while still working great the STM32F103 is "quite an old" chip by now. There have been several revisions on even basic things such as the SPI and I2C peripherals ever since then (and they provided huge improvements). If you could better state your requirements (especially in terms of memory & CPU resources) we might be able to recommend a "better" chip to you.
    But keep in mind that this would just be optimizing: µGFX will definitely run just well within the environment that you described.

    µGFX also allows you to compile your resources (eg. images) directly as part of the application itself using GFILE's ROMFS so you don't have to fiddle around with linker scripts.

  8. I fully agree with @inmarket here. We've yet to come across a C-Compiler that can't handle µGFX. We're running this project for over 7 years now and never encountered any issue on this end of things.

    As before: We're happy to help where we can - but you need to provide a bit more information. 

  9. Hello & welcome to the µGFX-Community!

    The Linux framebuffer driver is meant to directly operate on the framebuffer memory provided by the Linux kernel (if this feature is enabled). It's a device such as /dev/fb0 (or similar) that the Linux kernel provides as a framebuffer.
    If you do not want to use this framebuffer but render to a different display you'll have to provide a GDISP driver for this.

    As you mention SPI I assume that you have a dedicated display controller. In that case, check whether your display controller is already supported by the µGFX library. Otherwise you'll have to write your own driver.

  10. This is most likely a mismatch of the color formats.

    Check the color format configuration of your GDISP driver (eg. /drivers/gdisp/RA8875/gdisp_lld_conf.h). It defaults to RGB565.
    You have to ensure that the display controller on the other end is using the same color format as specified in the GDISP driver configuration.

  11. Hi,

    Unfortunately, we never worked with CubeMX enerated Makefiles ourselves. However, there are plenty of community members that did this successfully. As it's Makefile based you should definitely be able to just follow the official Makefile guide that you quoted in your post. 

    Maybe someone like @cpu20 could help here (he's this community's IDE expert).

  12. That sounds an awful lot like an issue in / related to the GDISP driver that you're using.

    You can use the GDISP TestStub driver to compile & run with that. It's an empty driver that doesn't do anything but allows to pass compilation of the GDISP module. This way you can ensure that the rest of the system is running properly.

  13. 15 hours ago, kpapr1 said:

    I don't see "GFX_NEED_GDISP" anywhere in my gfxconfig.h, but I have enabled this option -->    "#define GFX_USE_GDISP                                TRUE".

    You're using an older version of the library. We'd recommend using the latest master branch of the official repository or getting the latest stable v2.9 release from the downloads section.

  14. Have a look at the various GWIN (and widgets) documentation. Especially the /demos directory that comes as part of the library might be a valuable resource. the /demos/modules/gwin and /demos/applications applications will demonstrate the proper use of the event system to dispatch widget events.

×
×
  • Create New...