|
FOROS PROFESIONALES
WINDEV, WEBDEV y WINDEV Mobile |
| | | | | |
| Iniciado por guest, 21,sep. 2016 16:20 - 3 respuestas |
| |
| | | |
|
| |
| Publicado el 21,septiembre 2016 - 16:20 |
Hi,
In ajax tables:
Code for Row Selection of table ...[server]... -> is ALWAYS Ajax enabled and cannot be changed.
Now say you want to run from here/or call code that must NOT be Ajax Enabled.
If you use the button technique - calling a Button with NON Ajax code - with ExecuteProcess it will not work ...
WB seems to remember that it all started from a AJAX Area and code in the NON Ajax Area( the button) will not work - if it is not compatible with AJAX !!!
Any Ideas ?
* hope my message makes sense
Steven Sitas
www.alpha360.biz |
| |
| |
| | | |
|
| | |
| |
| Publicado el 21,septiembre 2016 - 19:41 |
Hi
Yes thaty is true. I tried adding going to another row with keyboard arrows. That was a nightmare . Got it working but with an ajax server call so verry slow.
This is problably a drawback form the one click ajax stuff. Better use looper and build a table that way. Then there are lots of things you can change and have control over.
regards
Allard. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 22,septiembre 2016 - 09:31 |
Hi,
You can use a timer function to trigger the Non Ajaxbutton. When you click your row, you start a timer in Java code (150ms).
In that piece of code that is called about 150ms later you can Execute the click of the non-ajax button.
Uncle Pete had explained this in some post I think ?
PCSoft should build this kind of call into the framework and add more different event to the controls in Windev. Maybe in the next version ?
Danny |
| |
| |
| | | |
|
| | |
| |
| Publicado el 22,septiembre 2016 - 10:55 |
Hi,
thanks everybody for the suggestions.
I finally changed the way "I was working/thinking" and moved on ...
If I had a debugger that would work with browser code also and inspect the values of GLOBAL variables in browser code, I would have found the problem a lot sooner.
To say it in a few words - you must be careful with Global variables that you change in server code, because "the same variable" may have not been changed in the Browser.
This is something WELL known _and_ I thought that the technique with the Button and Execute would solve the problem. This is actually what Uncle Pete describes in his post.
But this is wrong (or at least it is NOT the complete story).
What showed me the problem, is a post by Piet Van Zanten.
You can find it here: http://27130.foren.mysnip.de/read.php…
It actually talks about hidden fields, but there are other places also affected with this Server/Browser Duality. So always use Ajaxecute ...
Steven Sitas
www.alpha360.biz |
| |
| |
| | | |
|
| | | | |
| | |
| | |
| |
|
|
|