Timeline for VisualForce variables behaving badly
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 3, 2018 at 15:45 | answer | added | Wouter van Wageningen | timeline score: 0 | |
| May 3, 2018 at 5:12 | comment | added | Wouter van Wageningen | After removing a lot of code and making things a lot simpler, I found that using apex:actionsupport (onchange) with apex:input does not generate what you would expect it to do. Instead of calling the controller method every time, it only does it on the first change of the value. After removing the actionsupport and adding a onchange to the apex:input, I'm seeing better behaviour. I'll need to do more testing, bit for now, this seems to be the way forward. | |
| May 3, 2018 at 5:08 | comment | added | Wouter van Wageningen | After entering checkScanValue(), allowScan should be false and never turn true again. But I'm not seeing this. I had some Rendered="{!allowScan}" in the VF code, but those parts never disappeared. | |
| May 3, 2018 at 0:56 | history | edited | Daniel Ballinger | CC BY-SA 4.0 | Format code members |
| May 3, 2018 at 0:55 | answer | added | Daniel Ballinger | timeline score: 2 | |
| May 3, 2018 at 0:48 | comment | added | Thomas Taylor | Can you say more specifically what you're seeing happen/not happen in your page? Why do you say that those variables are not getting the correct val;ue assigned? What value should they be assigned and what would that do on the page? | |
| May 3, 2018 at 0:18 | history | edited | sfdcfox | CC BY-SA 4.0 | added 3 characters in body |
| May 2, 2018 at 23:32 | review | First posts | |||
| May 3, 2018 at 1:31 | |||||
| May 2, 2018 at 23:32 | history | asked | Wouter van Wageningen | CC BY-SA 4.0 |