Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. PODeadlock when closing thread
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmghie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODeadlock when closing thread
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think you are absolutely right. There is a reason, however, why I chose this approach. If I chose the synchronous approach, the WaitCommEvent() method would block my thread until an event specified by the mask would occur. This means that I would not be able to close my thread if no event occured, right? Or maybe it would be enough to close the serial port handle and the function would return then (with exception)?
      singulars
      1. PO
      1. USMariusz Schimke
    2. COOn the other hand, I create two independent threads for this allows me to wait for a device's answer. Let's say I communicate with a modem. I write eg the "AT" command and I expect the modem to respond with "OK" or "ERROR". I reset an event (TEvent), call the WaitForSingleObject() method which returns when the event is set by the reading thread's OnRead method. If there was only one reading/writing thread, I would have to block the main application's thread to do the same :(. Am I right?
      singulars
      1. PO
      1. USMariusz Schimke
    3. COIf there was only one serial port to communicate on I would probably use asynchronous I/O in the main thread. If there were more than one I would probably use asynchronous I/O in one worker thread. Also, whether to use synchronous or asynchronous I/O in a background thread depends on whether you know beforehand when data is to be received. If you just receive answers to requests, why use WaitCommEvent() at all? Just read directly, after setting up sensible timeout values. If the other side could send at any time WaitCommEvent() makes more sense of course.
      singulars
      1. PO
      1. USmghie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload