Viktor,
simple multiple calls to WIN_CREATEFONT(), even
in single thread.
Sorry but I do not understand.
WIN_CREATEFONT() only has a live font eliminating the prior and this font is
saved for each DCS to make sure it is removed.
It's the logic of the existing function maybe have to be called WIN_CREATEFONTWPDC :) because it is not a function of creating
generic fonts rather to print fonts with TPrint()
--
Xavi
Viktor Szakáts escribió:
Hi Xavi,
You've converted the static variable to a thread
protected variable, but this doesn't solve the
real problem. The real problem is not MT, but
simple multiple calls to WIN_CREATEFONT(), even
in single thread.
IMO we don't need any such heavy tricks here.
Simply the interface should be descrambled so
that it gives back proper handles to caller code,
which stores these handles, and they're getting
released when going out of scope. Or, if two
Windows handles belong to one Harbour level
object, a helper structure should be used
in garbage collector functions and this way
it's possible to release both when the variable
goes out of scope.
[ I'm also not sure if it's correct to use
thread local variables is garbage collector
code, but it looks a bit suspicious, since
a value may be passed to other thread and
live there from that point. ]
Apologize if I'm missing something here, which
makes this case special, but I can't see it ATM.
Brgds,
Viktor
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
