Rank: Member
Groups: Guest
Joined: 1/7/2008(UTC)
Posts: 28
|
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. Edited by user Thursday, May 22, 2008 2:27:08 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 8/3/2003(UTC)
Posts: 1,070
Thanks: 1 times
Was thanked: 12 time(s) in 12 post(s)
|
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. |
|
|
|
|
|
|
|
Rank: Member
Groups: Guest
Joined: 1/7/2008(UTC)
Posts: 28
|
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: Guest
Joined: 1/31/2005(UTC)
Posts: 458
Was thanked: 5 time(s) in 5 post(s)
|
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. Edited by user Tuesday, March 11, 2008 9:41:33 PM(UTC)
| Reason: Not specified |
|
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.