Discussion on Basic Thread Manager


MateuszManaj does not currently provide support for this item.

7 comments found.

Hi, I need some help, Invoke and MethodInvoker cannot resolve by compiler.

And if I don’t want to use prgress bar, how can I disable it?



MethodInvoker is object placed in System.Windows.Forms so you want to include this lib, like: using System.Windows.Forms;

Invoke extension method is placed in pretty much every control such as buttons, labels and so.

If you want to disable progressbar you want to use StartSimple() method rather than Start() Did you check documentation ?

Keep well!

Hi MateuszManaj,

Great piece of work you’ve done here with the Basic Thread Manager.

Is there a way to implement the FormBorderStyle.FixedToolWindow and a form shadow for the Progress Bar form such as here: Maybe an option to turn shadow on or off?

Thank you for any consideration on these features.

Hi there, Thanks and yes. It’s simple to do this in Basic Thread Manager. Just set window property like // ... var sgt = new BasicThreadWorker(); sgt.Maximum = 100000; sgt.View.Trayable = true; // This is how to get form property from BTM sgt.View.FormBorderStyle = FormBorderStyle.FixedToolWindow; sgt.UseTaskbarProgressBar = true; sgt.ThreadMethod = delegate { // ...

About form shadow – it can be done by WinAPI. This article was written in 2007 so many things changed. I consider this option in next release or maybe if you give me more use cases for that :)

Keep well!

Also would like to ask if there is a way to have the progress bar look more like the standard 2d/3d bar as apposed to yours having a flat look?

Yes, this is a way to achieve this flat effect. You can define your own progressbar class like in here: and modify while it’s repainting.

Like above, if you give me more practical examples than I consider this option in next update :)

Keep well!

Can I use in VB ? can you show me the code how you use it on vb .net code ?


Hi, I response to this question in mail.

error in visual studio 2013

TaskDialog feature needs to load version 6 of comctl32.dll but a different version is current loaded in memory.

how can I do??

Sorry, I have created this in VS 2010 not in 2013.

Hi, compilation it’s ok. I only target all cpu. I have this error when i start debug.

taskDialogMain.Controls.Add(simpleIterationBtn); taskDialogMain.Controls.Add(taskbarProgressBtn); taskDialogMain.Controls.Add(fileDownloaderBtn); taskDialogMain.Controls.Add(strOperationBtn); taskDialogMain.Controls.Add(taskQueuesBtn); taskDialogMain.Controls.Add(prgbarRuntimeStyleBtn); taskDialogMain.Controls.Add(eventsBtn);

taskDialogMain.Icon = TaskDialogStandardIcon.Warning;

OverflowException occured when: taskDialogMain.Show();

System.OverflowException non è stata gestita HResult=-2146233066 Message=Overflow di un’operazione aritmetica. Source=mscorlib StackTrace: in System.IntPtr.op_Explicit(IntPtr value) in Microsoft.WindowsAPICodePack.Dialogs.NativeTaskDialog.AllocateAndMarshalButtons(TaskDialogButton[] structs) in Microsoft.WindowsAPICodePack.Dialogs.NativeTaskDialog.MarshalDialogControlStructs() in Microsoft.WindowsAPICodePack.Dialogs.NativeTaskDialog.NativeShow() in Microsoft.WindowsAPICodePack.Dialogs.TaskDialog.ShowCore() in Microsoft.WindowsAPICodePack.Dialogs.TaskDialog.Show() in BasicThreadManagerSampleApp.Program.Main() in c:\Users\SysAdmin\Downloads\codecanyon-6492622-basic-thread-manager\VS 2010 Project\BasicThreadManagerSampleApp\Program.cs:riga 67 in System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args) in System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args) in Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() in System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) in System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) in System.Threading.ThreadHelper.ThreadStart() InnerException:

I replaced Windows-API-Code-Pack-1.1 with new control and your project work very well without Windows-API-Code-Pack-1.1. Windows-API-Code-Pack-1.1 isn’t necessary. Now Basic Thread Manager work without Windows-API-Code-Pack-1.1. Good it’s Thread support from your control. Now Basic Thread Manager work without this dependence.

I solve the problem with one line of code and little changes.

View.winProgressBar.ShowInTaskbar = true;

and my new control made all.

You made a very good work. If you take away Windows-API-Code-Pack-1.1 your code work on 32/64 and all .NET. :)

KISS principle

KISS is an acronym for “Keep it simple, stupid” :)

Great!!! GLWS!

Thank you :)