Threads - GetList anomaly using VALID
Posted: Thu Mar 10, 2022 3:09 am
using a thread to open a new DCDialog window, I encounter a problem using GETs with the VALID clause
when I have 2 windows running, and I position myself on the GET field that contains a VALID, I can not continue on the other window
if I click on the second window, the cursor returns me to the GET of the first window that has the VALID that returns .F. (for example empty field)
I used the DCREAD badly in every prg ?
from xbase manual:
Multithreading issues All events are stored in a so-called event queue and AppEvent() retrieves events from this queue. If a program uses multiple threads, it is important to know that event queues have thread-local scope. When Xbase Parts are created in different threads, they are retrieved from different event queues by AppEvent() (3rd parameter oXbp ). As a result, each thread that creates an Xbase Part must call AppEvent() so that events for this Xbase Part can be processed.
when I have 2 windows running, and I position myself on the GET field that contains a VALID, I can not continue on the other window
if I click on the second window, the cursor returns me to the GET of the first window that has the VALID that returns .F. (for example empty field)
I used the DCREAD badly in every prg ?
from xbase manual:
Multithreading issues All events are stored in a so-called event queue and AppEvent() retrieves events from this queue. If a program uses multiple threads, it is important to know that event queues have thread-local scope. When Xbase Parts are created in different threads, they are retrieved from different event queues by AppEvent() (3rd parameter oXbp ). As a result, each thread that creates an Xbase Part must call AppEvent() so that events for this Xbase Part can be processed.