Is there a known reason why a control on a kinetic screen shows itself in application studio, it is not hidden, but it does not show when the screen renders? I have a combo box that just will not render no matter what. I can move it around to other areas and next to controls that do show, but it will not show itself.
…
After typing this question, I deleted my control and just added a simple button, and that won’t even show on the screen. So now nothing I add to this screen will render. I’m guessing I’m rebuilding the screen.
I was able to at least copy and paste the controls from the old screen to the new screen, so I’m not starting from scratch, but I am rewiring everything. I would have had a breakdown if this wasn’t my normal experience with Application Studio.
I’m pretty sure @bconner is looking for examples of when layers break like this. They are working on trying to understand how and why stuff like this is happening.
This kind of thing happens to me probably 40 times a day. I’m constantly refreshing my screen because application studio won’t save. I did find some workarounds to some of these issues. But right now, I just loaded the screen, opened up an event, added an event-next to the event and application studio won’t save the layer. This is my normal experience. I’m constantly saving because that tells me when it breaks.
Ah yeah I worked with the App Studio team on this a few months ago. We found errors in the console log generated after changing some properties on components or working with events. Once those errors hit saving didn’t do anything anymore.
They generated about 6 bug reports from our conversations and I would assume are actively working on them (they are internal so I have no insight to them).
Do you have a 2025.1.10+ system available to develop in and see if you find improvement in the resiliency of Application Studio?
Can you send us a copy of that layer - We’d obviously prefer you do not have to start over, we can probably remediate it given a copy to see what’s wrong with it.
Brian, can I send you a layer where the text boxes show the name of the baq field from the data view instead of the explicitly defined label? I have been struggling to report this through support for 3 years now (not exaggerating) but they can never reproduce it.
We have a quality project running over the summer to fix any known studio lockup or broken layer issues, however we don’t have a large list of these and so we’re seeking anyone who can demonstrate studio becoming unresponsive, unable to save, or otherwise not taking changes you are making into the layer. Particularly broken layers we would like to see the actual layer - if you are circling getting anything like that reported with support due to reproducibility give me a ping with the layer and we can unblock the process.
support is best of course, but you can also ping me with a case # and layer if it’s circling on its way to us (which has been happening sometimes since they are hard to reproduce). Most of you probably have my email already but it’s bconner at you know what
but it’s bconner at you know what