I have published the new version to test and I’m bracing for the deluge of bug reports and requests 
One thing I have noticed, especially on V1 panels is the small amount of memory can easily be consumed and that causes a crash. The V2 panels are better as they have more memory, but al ot of images can still be troublesome.
Yes i’m using a V2 thankfully.
I will do a stress test for app next week, I am away from home till Monday. Thank you so much!
Going to test V1.0.0 right now, would you like like bugreports in github or somehwere else?
Either here or GitHub. I tend to check here more frequently, but GitHub does allow individual issues to be kept organised instead of spread around.
I don’t know how yet but i’ve found a way to kill the whole webinterface of the button+ when i connect it to your mqtt(with websocket) and send my config. It has something to do with the preview rendering of svg’s, but even after removing them i’m still stuck.
I havent followed this topic in a while, but man-o-man m8, what a great improvements you have made! Cheerio m8!
Are you talking about the Button + built in web interface?
SVG support on the Button + is a bit limited, so they have to be very simple.
If the panel is restarting in a broken state due to configurations issue, you might need to reset it first using the buttons on the bottom of the panel.
Yes I am, it even seems to happen with the default config that your app pushes as the introduction screen. Thankfully that web interface is not mandatory and your apps seems to work quite well.
Ok, I have not seen that before and I quite often use the web interface to test bits. Maybe contact Button + support to see if they have any ideas.
I have published a new test version with fixes for the reported crash logs
Overall things I wanted to mention, I was testing the interface, not real way how it funtcions
I didn’t get the Purpose on the dropdown configurator where you can select 1-2-3-4 rows to edit simultaneously on one page. This is very confusing as this basically the same view as Group view.
IT would be great if after editing the configuration of a row, you could have a back button to return to the Group view, It would be much cleaner.
Big On/Off Labels on the Group view is. This is a test plane where you overview what you configured, so Overall On/Off Switch for all Rows simultaneously will make more scene.
And it terms of testing button functionally it would be better if you output what is actually going to render the button, if it is text or SVG
The place holders for led lights are way too dark and almost undistuguashable from background, I was barely able to locate it to press, I think you have to add a contrast boundary box around it.
To followup Venxir, I noticed that button rendering fails when you log in to WebUI back on 0.7.44 version. The only thing helped was a complete reset of button. As for 1.0.1 version of the app the problem is still there.
One more thing - click button functionality. If no actual device selected the only option is “Toggle Direction”. Not very clear what it means - for example I am going to do linking each button to advanced flow, but how would it react?
I think that the best idea here is to hide more advanced logic here. Corrent me if I am wrong
Actual button, acutally send two events - click, release (long press - actually repeated event on click)
Single click goes with - click, release
Double - click, release, click, release
Long press - click, click, click… release
If you run behind the scene script that captures “click and release” events that will make more scense, as right now (I am not certain) Single click will override Long Press as it fires first.
Adrian_Rockall, I would say that Click, Long Press, Double Click functional is awesome, just as it is supposed to be
I started to dig deeper and right now figured out a bug for the Display module. When I configure default page 0, on the very bottom I set a current page. On the 0.7.xx versions this value was rotating depending on what page is actually selected, but for 1.0.1 it show “Page 2” for Page 1, “Page 3” for Page 2, etc. Something wrong wit the internal counter.
The Display module config is also missing the configuration of actual physical buttons. So they are always set for Next/Prev Page
