Gradient + Stroke Export Rasterized Output in Qt Bridge for figma

Qt Bridge → Qt Design Studio (Qt for MCUs project)

Test Cases and Results

Case 1)

-Figma setup: Rectangle + Solid Fill + Stroke
-QDS result: Rectangle without stroke (only fill remains)

Since Qt for MCUs does not support the border property on Rectangle, the stroke was removed, but the solid fill remained after export.

Case 2)
-Figma setup: Rectangle + Linear Gradient Fill (GradientStop includes opacity) + Stroke
-QDS result: The entire object was rasterized as an image.

 Qt for MCUs supports Linear Gradient and GradientStop RGBA colors, but there may be some limitations:
-Opacity Stop Issue
 GradientStop with opacity may not be supported in MCU native gradient, causing rasterization.
-Combined Effect Handling
 Gradient + Stroke combination might be treated as an unsupported complex effect, leading to rasterization.
-Conservative Fallback Handling
 Qt Bridge may choose to rasterize when it encounters ambiguous cases to ensure safe rendering.

Figma link : https://www.figma.com/design/fq4xfllHN2uV6EPzA9yqF8/branch/NDmzL8nBPq6X9Kb6q0i8yw/QT_QA_250619?m=auto&node-id=1006-2&t=0z1KwoV1nZScpbTu-1

Questions
1)Why is stroke only removed in Case 1, but the entire object is rasterized in Case 2?
2)Does GradientStop opacity stop trigger rasterization?
3)What is the exact policy in Qt Bridge for handling gradient + stroke combinations?