Displaymanager new project!

[jgu1]

Hi!

I am starting on a new project, using displaymanager. I have to be able to switch an output on and off by pressing a botton, and I have to create some more botton, this is only the start. As you see in Scene0 I have made two botton, in the beginning when I simulate borth botton was shown in the display on the 2D screen, also when I compile to chip and I was able to switch the output on and off by toggle the botton, but suddently the disapear from the 2D screen and when I touch the one botton both output switch on. What Have I done wrong please?

One wish more, how can I when I press one of the botton, change the bagground on the botton from red to green and the text also have to change to ON and when I press again go back to red bagground and the text OFF.

Hope for some help, thank´in advance

Br Jorgen

[BenR]

Hi Jorgen,

Your first button toggles GPIO0.

Your second button also toggles GPIO0 and underneath the decision sets GPIO2.

To change the button colour you simply call the Button component macro ModifyColour with index 1 for the background colour and index 2 for the text colour. The Redraw parameter decides if the colour change is drawn immediately but this will remove the default text so might be better to just use the text set function to redraw after the colour change.

Here's an example.

Screenshot 2026-10-01 110018.png (84.14 KiB) Viewed 152 times

There is some wierdness for me on my home PC so I'm seeing if I can replicate with a fresh project.

You shouldn't need the while touched loop unless you never want repeat touches and the second check for touch in your main macro isn't needed. If you need longer delays between touches then instead increase the Touch Repeat rate property of the Display Manager component.

Untitled.jpg (84.69 KiB) Viewed 152 times

[jgu1]

Hi Ben!

Thank you very much for your quick reply.

Yes, regarding the mistakes I made, I clearly wasn’t paying enough attention! I have now got the colours and text changing correctly, so I have learned something new.

However, as you can see, even though I have two buttons in Scene 0, only one of them appears in the display in the 2D panel. The same thing happens when I start the simulation.

When I compile the program and run it on the chip, the colour change and text work correctly, but the display is extremely slow. It also looks as if button 2 has somehow “exploded”. The actual button is not visible, but the text is scattered across the bottom of the display.

Am I doing something wrong again?

Jorgen

[BenR]

I've managed to dig in and find the cause of the missing button. Bizarrely it's to do with the specific background colour you've specified!

I've now fixed this in the component source, it was a very corner case issue with my serialised data parser. The first byte of the colour was matching up with a command code and corrupting the first item in the list.

I don't currently have access to my work PC so here's the file you can manually put into your "C:\ProgramData\MatrixTSL\FlowcodeV11\Components" folder.

DisplayManager.fcpx

(719.17 KiB) Downloaded 6 times

Hopefully this also fixes the second issue you're having.

I'll get this pushed to library updates tomorrow.

[jgu1]

I can now see the second button . But the display is still very slowly to update the button, but if I delete the changing bagground color and only change the text change color it is a little faster. In the buttons under the text a thin line is there in both button and on the right side of the buttons, it looks as if someone has bitten a piece off, or as if it has somehow broken.
If it is better for you, have a look when you are on the work PC if it is something you can fix
Jorgen

[BenR]

The line under and to the side is the drop shadow for touchable items. You can turn it off if you like.

Screenshot 2026-10-01 195403.png (20.7 KiB) Viewed 90 times

You could add a small rectangle on top of the button and change the colour of that. The smaller the area to redraw the faster it will be.

Screenshot 2026-10-01 195646.png (3.69 KiB) Viewed 90 times

I see you're using the fast SPI and the Fast pixel queue so I'm surprised it's as slow as you're saying. I'll check that the optimisations are in place for filling rectangles on that display.

[jgu1]

Hi Ben.

Once again, thank you very much for your help. That solved the problem with the line.

And thank you also for your detailed Display Manager videos on YouTube. I have watched them many times, and they have been very helpful.

I understand about the update speed of the buttons.

In the meantime, I changed the project yesterday so that the display has square corners instead of rounded corners, and I have almost finished it. I just need to create the programs for the last two buttons. Everything is working fine, and it looks really good on screen with the Display Manager

However, the “Compressor” button keeps toggling on and off by itself, but only on the hardware. Could this be something related to the S3 models? I experienced exactly the same thing in another project that I tried converting to an ESP32-DE1, and the problem disappeared there.

You are probably wondering why I don't simply use the ESP32-DE1, but I need the additional I/O available on the S3.

Perhaps you could give me a suggestion for how I can eliminate these “ghost touches” when nobody is touching the screen?



**** EDIT: "ghost touch solved, I try i the Properties for the XPT2046 change the setting Analog mode from single end to differencial Solved my issue ****

Please update the last display manager component

Many thanks again for your help.

Best regards,
Jørgen

[BenR]

Hi Jorgen,

Excellent that sounds like great progress. The latest DM component is also now on the library updates system and I've added some new template files for the DM with more to come soon.

Shout if you need anything else

[jgu1]

Thank you for the information, Ben. I’m looking forward to seeing the new features in Display Manager, and perhaps also a YouTube video introducing the new possibilities.

Have a nice weekend.

Jorgen