|
|
Rank: Member
Groups: Member
Joined: 1/8/2008
Posts: 28
Points: 84
|
Code:
_ResizeTransform = New Aurigma.GraphicsMill.Transforms.Resize(CSng(_bitmap.Width * dblresRatio), CSng(_bitmap.Height * dblresRatio), Aurigma.GraphicsMill.Transforms.InterpolationMode.HighQuality)
AddHandler _ResizeTransform.Stopped, AddressOf _ResizeTransform_Stopped
_ResizeTransform.Priority = Threading.ThreadPriority.BelowNormal
_ResizeTransform.SynchronizationMode = Aurigma.GraphicsMill.SynchronizationMode.Sync
The code _ResizeTransform.SynchronizationMode is giving error of A first chance exception of type 'System.NotImplementedException' occurred in Aurigma.GraphicsMill.dll Please submit case if you are using async mode. Please advice.
|
|
Rank: Advanced Member
Groups: Administration
, Member
Joined: 8/3/2003
Posts: 607
Points: 651
|
Hello,
You do not need to change the value of SynchronizationMode property. The property has Sync value by default, and this property is obsolete.
If you need to use multi-threading approach in your application, you need to use standard System.Threading classes along with Graphics Mill ones.
Sincerely yours,
Dmitry Sevostyanov.
|
|
Rank: Member
Groups: Member
Joined: 1/8/2008
Posts: 28
Points: 84
|
Dmitry wrote:Hello,
You do not need to change the value of SynchronizationMode property. The property has Sync value by default, and this property is obsolete.
If you need to use multi-threading approach in your application, you need to use standard System.Threading classes along with Graphics Mill ones. Hi, Due i read from the website saying the .NET version is supporting multi-threading. And that code was modified from the example. Just wondering, do you have any sample on the Multi-Threading beside the current obsolete property sample? Please advice.
|
|
Rank: Advanced Member
Groups: Administration
, Member
Joined: 1/31/2005
Posts: 388
Points: 409
|
Hello,
Yeap, Graphics Mill for .NET supports multi-threading. For example, all static methods are thread safe and internal architecture of the library had been developed to be used in multi-threaded enviroment. So we have no changes here.
As for SynchronizationMode property - it was just some sort of helper, and we decided to remove it. It will be better (for code understanding, maintaining and reuse) to use standart .NET framework classes.
Could you describe what operations you want to be executed in a separate thread and for what reason? I will be glad to assist you with the code sample.
Best wishes, Alex.
|
|
|
Guest |