Hi,
I've a GUI design created in ESD which I'm targeting on my STM32H7 board using FT813. I've run into a few questions on target that are causing problems.
1. I have a custom widget+actor using a Scroll Layout with Scissor enabled. The wanted effect is animated opening of a side window (think of a drop-down menu on many PC apps). This works well in ESD simulator, but using generated & exported code on target the appearance is different. My question: if I put a Linear Layout within Scroll Layout and enable Scissor in the Scroll, how does scissoring work for the nested Linear Layout?
2. Related to the above, my general question is how do scissor/clip and overflow work in a HIERARCHICAL sense? So far, I have seen that overflow and clip appear to make no difference to anything and I can't understand how these are supposed to work when apparently scissor is the accepted way to actually implement clipping?
3. On another topic, regarding asset loading. As a simple way to avoid the need for FATFS (which I'm using for other things), I have a plan to modify the HAL-abstraced FATFS file loader to return const initialised data, with a few .astc files defined as hex binary data there. In this case presumably I only need to convert the raw .astc to hex and can skip the generation of flash-initialisation .bin files? I think this should work - but have I missed anything?
Thanks in advance,
Nick
can you share the picture or ESD project here? It will be helpful to understand your question.
Hi Paul,
I was really hoping for a general explanation of the points that I had asked about, having overcome the problem that I initially encountered.
Thanks,
Nick