Desktop Window Manager wrapper

[Stanimir Stoyanov]

In case you are writing a program that need to interact with the Desktop
Window Manager, manage Glass or blur on your forms/windows, you might want
to check the series of posts I am writing on this matter at
http://stoyanoff.info/code/glasslib/.

The library (GlassLib) is open source and can be compiled for Windows Forms,
Windows Presentation Foundation, or with no dependencies whatsoever (it
operates with window handles in this case).

Best Regards,
Stanimir Stoyanov | www.stoyanoff.info

 

[Pavel Minaev]

In case you are writing a program that need to interact with the Desktop
Window Manager, manage Glass or blur on your forms/windows, you might want
to check the series of posts I am writing on this matter athttp://stoyanoff.info/code/glasslib/.

The library (GlassLib) is open source and can be compiled for Windows Forms,
Windows Presentation Foundation, or with no dependencies whatsoever (it
operates with window handles in this case).

Great stuff, but it seems like precisely the right case to use
extension methods to transparently introduce those new members on Form
class. E.g. instead of:

Dwm.Glass[form] = new DwmMargins(100, 4, 8, 20);

something like:

form.GetDwm().Glass = new DwmMargins(100, 4, 8, 20);

 

[Stanimir Stoyanov]

Thanks for the suggestion, Pavel. I will take it into consideration and work
on a version with extensions but still leave properties for use in legacy
(well, older) versions of Visual Studio and .NET Framework.

Best Regards,
Stanimir Stoyanov | www.stoyanoff.info

In case you are writing a program that need to interact with the Desktop
Window Manager, manage Glass or blur on your forms/windows, you might want
to check the series of posts I am writing on this matter
athttp://stoyanoff.info/code/glasslib/.

The library (GlassLib) is open source and can be compiled for Windows
Forms,
Windows Presentation Foundation, or with no dependencies whatsoever (it
operates with window handles in this case).

Great stuff, but it seems like precisely the right case to use
extension methods to transparently introduce those new members on Form
class. E.g. instead of:

Dwm.Glass[form] = new DwmMargins(100, 4, 8, 20);

something like:

form.GetDwm().Glass = new DwmMargins(100, 4, 8, 20);

 

[Leon Jollans]

do you need to support "legacy" environments? we're by definition only
talking about vista and above, right?

Thanks for the suggestion, Pavel. I will take it into consideration and
work on a version with extensions but still leave properties for use in
legacy (well, older) versions of Visual Studio and .NET Framework.

Best Regards,
Stanimir Stoyanov | www.stoyanoff.info

In case you are writing a program that need to interact with the Desktop
Window Manager, manage Glass or blur on your forms/windows, you might
want
to check the series of posts I am writing on this matter
athttp://stoyanoff.info/code/glasslib/.

The library (GlassLib) is open source and can be compiled for Windows
Forms,
Windows Presentation Foundation, or with no dependencies whatsoever (it
operates with window handles in this case).

Great stuff, but it seems like precisely the right case to use
extension methods to transparently introduce those new members on Form
class. E.g. instead of:

Dwm.Glass[form] = new DwmMargins(100, 4, 8, 20);

something like:

form.GetDwm().Glass = new DwmMargins(100, 4, 8, 20);

 

[Pavel Minaev]

do you need to support "legacy" environments? we're by definition only
talking about vista and above, right?

Vista was released in 2006, and predates .NET 3.5 and C# 3.0. So, yes,
it makes sense to support .NET/C# 2.0 as well.