Page 1 of 1

checkbox remains on screen after changing format

Posted: Wed Jul 13, 2016 5:20 am
by t.s.h
I have the following problem I can't solve at the moment.

In a selection screen I have some input fields, a grid and a checkbox.
Checkbox 1_2016-07-13.png
Checkbox 1_2016-07-13.png (12.64 KiB) Viewed 512 times
After choosing a record and jumping in the next screen the checkbox remains on its position.
Checkbox 2_2016-07-13.png
Checkbox 2_2016-07-13.png (13.22 KiB) Viewed 512 times
Any idea how I can avoid this behavior?

Re: checkbox remains on screen after changing format

Posted: Wed Jul 13, 2016 5:54 am
by dieter
Hi Thorsten,

are you sure that this is the same checkbox? Could it be that this checkbox is in the new format? I former releases i had problems by copying widgets from one screen to another. Sometimes i had effects of strange behavior with this copied elements. When you open your second format in the visual designer, what says the element list? Does this element appear in the element list? Maybe you can rearrange the elements by using the Auto Arrange Button. Maybe this helps.

If not, you can use the debug functionality in your browser. In Chrome you get this by "Ctrl + Shift + i". This should help you to recogneize from where the checkbox comes.

Dieter

Re: checkbox remains on screen after changing format

Posted: Wed Jul 13, 2016 6:57 am
by t.s.h
Hi Dieter,
thanks for your answer. It seems to be the same checkbox. It also keeps the check or unchecked state.
It does not appear in the element list of the second screen also after an auto arrange
Checking the html output with chrome it seems to be really the same checkbox. At least it has the same id.

Thorsten

Re: checkbox remains on screen after changing format

Posted: Wed Jul 13, 2016 4:10 pm
by Scott Klement
The idea that it might be "left over" doesn't make much sense to me. You should check to see if the "overlay" or "show as window" properties are on. It's very possible that you are putting one format on top of the other.

If you suspect that this is a bug, please send it to Profound Logic Support instead of posting it here.