View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000083 | JEDI VCL | 00 JVCL Components | public | 2002-04-30 08:10 | 2002-06-06 15:30 |
Reporter | user81 | Assigned To | user81 | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Summary | 0000083: implement JvThread more 'nativly' | ||||
Description | From: Marian Wendt <Marian.Wendt@inca-gmbh.de>: Compliment to the idea of implementing a thread as a component. BUT: The Thread ID which one needs to manipulate the thread (priority, suspend)at the Execute method (and only here) is returned. A later time for the determination of this ID isn't available so that one is forced to carry the ID consumingly. In the source gets clear that this makes, the withdrawal start several instances with the possibility to JvHideThread required. However, I regard the approach as impractical since the JvThread component can be used just the same well in the case of several similar Threads. Please think about to implement JvThread more "nativly" with all the possibilties of manipulation without carring an ID. | ||||
Tags | No tags attached. | ||||