Using OCX controls in .NET
-
MS Toolbar Control in mscomctl.ocx has a HotImageList property where as the .NET ToolBar doesn't. Are there any disadvantages or problems using the MS Toolbar Control, or any other COM Components and distributing the mscomctl.ocx with my .NET application? Jerzy
-
MS Toolbar Control in mscomctl.ocx has a HotImageList property where as the .NET ToolBar doesn't. Are there any disadvantages or problems using the MS Toolbar Control, or any other COM Components and distributing the mscomctl.ocx with my .NET application? Jerzy
This puzzles me too. But since they brought XP out, they have sorta abandoned the cold/hot image list stuff from toolbars. For example IE 6 on XP does not use cold and hot image lists. Maybe they feel it's a dumb feature. Nish
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.
-
This puzzles me too. But since they brought XP out, they have sorta abandoned the cold/hot image list stuff from toolbars. For example IE 6 on XP does not use cold and hot image lists. Maybe they feel it's a dumb feature. Nish
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.
Agree, but what about using other OCXes, or using DLLs or unsafe code. Should we totally avoid using them and stick only with managed code? Jerzy
-
Agree, but what about using other OCXes, or using DLLs or unsafe code. Should we totally avoid using them and stick only with managed code? Jerzy
JerzyPeter wrote: Should we totally avoid using them and stick only with managed code? Not at all! The .NET framework is still incomplete in various areas. There is nothing wrong in invoking the API Nish
Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.