Continuation of "About the GUIX restrictions"

k.kaneko 161 Reputation points
2023-01-30T22:09:31.13+00:00

This is a continuation of my previous question "About the GUIX restrictions."(https://learn.microsoft.com/en-us/answers/questions/1108375/about-the-guix-restrictions).

A client of ours has contacted us.

The following comment, which you recently responded to, applies to both GUIX and GUIX Studio?

"There is no internal limit on the number of widgets or number of resources a project may contain."

I couldn't seem to write in a question that had an answer, so I asked it here.

Azure RTOS
Azure RTOS
An Azure embedded development suite including a small but powerful operating system for resource-constrained devices.
324 questions
{count} votes

Accepted answer
  1. Ken Maxwell 706 Reputation points Microsoft Employee
    2023-01-30T22:24:47.8133333+00:00

    @k.kaneko no problem with a new question. For GUIX Studio the only limit is the host PC memory, which is effectively unbounded. On the target side, the only limit is the amount of memory you have available on the target for control blocks and static resources. Widget control blocks are stored in RAM, resources are stored in non-volatile memory (FLASH). The GUIX runtime library does support the ability to allocate and deallocate control block memory dynamically, so if you have a very large number of screens and child widgets you can configure these screens to be dynamically allocated. Therefore in practice the limit that applications are most likely to run into is the limit on non-volatile memory for resource storage, namely fonts and images. Large Kanji fonts can take up a big chunk of FLASH.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful