Thanks
On Thu, 20 Sep 2018 13:25:55 -0500, John DeSoi via 4D_Tech wrote:
>
>> On Sep 20, 2018, at 11:40 AM, Chip Scheide
>> <4d_o...@pghrepository.org> wrote:
>>
>> I have been looking through the v16 and v17 documentation, I do not see
>> where it says that pasteboard commands do not work with/inside
>> pre-emptive threads.
>
> Every command that supports preemptive mode has a CPU icon under the
> "PROPERTIES" header (where it has the command number). You can click
> on that icon to get the full list:
>
> http://doc.4d.com/4Dv17/4D/17/Preemptive_3726273.999-2878208.en.html
>
>
>>
>> Also, IP sets, I also do not see any specific reference (one way or the
>> other) regarding IP sets and preemptive threads. I would assume, may be
>> the problem :), that since an IP set can be changed from outside the
>> preemptive thread that it would be a problem, just like an IP variable.
>
>
> I have not seen a discussion about it, but I assume IP sets and IP
> variables are totally different in this regard. All changes to sets
> are made through 4D commands which enables 4D to ensure they are
> thread safe. IP variables are memory references that code directly
> modifies.
>
> I did a simple test creating an IP set in a preemptive process and it
> seems to work. The compiler will generate errors if any method in the
> call chain has an IP variable.
>
> John DeSoi, Ph.D.
>
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive: http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************
---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
