Now in the screen, create the design of your choice
by clicking square icon. Under That, u can see all shapes.
Please note only to add text or Place image in the project
Synchronizing with Thunkable X
Now that you have done funking let us synchronize figma with Thunkable.
Note : Please tick the box in front of Try it Out. It is not appearing in the screenshot because of a technical issue.
Done with what? That imports the Figma file. But do the objects I’ve created in Figma become actual components in Thunkable? Or is it just a visual template/grid that I can use to then drag components on top of?
I Guess it is a visual template…i mean more of that… but components like Place Images and text which are supported in thunkable could be edited with the blocks figma section.
I add my figma desing on new UI. When I select the screen to add the thunkable from the asset menu, I couldn’t do anything on the screen. There is a too much delay. Did u get it? And how to delete figma file from the asset?
Great question @tatiang - for any element or vector that you import from Figma you can choose in Thunkable which component to assign it to with the following dialog:
Even without going through this step the blocks section for each imported component will allow you do things like event handling that you can do with our built-in UI components:
@lukas_b_98knm - this is just referring to the frame size you should use in Figma. My preference is to use a frame that’s the same size as the phone screen in Thunkable, we can handle all the scaling from there.
I figured this myself but I had what I can refer to as click sensitivity issue. When you have a rectangle inside another it becomes hard, at least for me, to select one of them in Thunkable designer. Is this something you encountered?
I know this is a side issue but I think it’s an important one for maybe a separate topic or bug report. Selecting one component when two or more components are overlapped is much harder than I expect each time. It seems like the tolerance for where you click to select a component might be too much. So when I have the top-left point of my mouse cursor on top of a component that is behind another, it doesn’t always select it; it often selects the component in front even though my cursor doesn’t seem to be touching it. I know, hard to picture!
icon.
