Reusable User Interface elements in Visual Studio
-
Hi. I am trying to make some reusable GUI components for several desktop application projects. These projects are all Windows (Win7), Visual Studio, C++ based. What do you think would be the best way to approach this problem? Right now i was thinking about one of these 2 ideas: - MFC ActiveX Control. - MFC extension Dll. So far ActiveX has the benefit of being able to be integrated directly in the VS resource editor and this would make the integration easier. On the other hand, ActiveX would allow only 1 GUI component per .OCX (am i wrong here? is it possible to incorporate more that 1 control in an .OCX file?) and this would mean that i would have to distribute a lot of .OCX files and it would just not look right. Can you tell me if ActiveX is still considered a "modern" way of doing things? I wouldn't want to use something that is about to be deprecated. Thanks.
-
Hi. I am trying to make some reusable GUI components for several desktop application projects. These projects are all Windows (Win7), Visual Studio, C++ based. What do you think would be the best way to approach this problem? Right now i was thinking about one of these 2 ideas: - MFC ActiveX Control. - MFC extension Dll. So far ActiveX has the benefit of being able to be integrated directly in the VS resource editor and this would make the integration easier. On the other hand, ActiveX would allow only 1 GUI component per .OCX (am i wrong here? is it possible to incorporate more that 1 control in an .OCX file?) and this would mean that i would have to distribute a lot of .OCX files and it would just not look right. Can you tell me if ActiveX is still considered a "modern" way of doing things? I wouldn't want to use something that is about to be deprecated. Thanks.
Please don't repost questions. You have already asked this at Reusable User Interface elements in Visual Studio[^] and got a first answer meanwhile. This avoids multiple threads about the same question.
-
Hi. I am trying to make some reusable GUI components for several desktop application projects. These projects are all Windows (Win7), Visual Studio, C++ based. What do you think would be the best way to approach this problem? Right now i was thinking about one of these 2 ideas: - MFC ActiveX Control. - MFC extension Dll. So far ActiveX has the benefit of being able to be integrated directly in the VS resource editor and this would make the integration easier. On the other hand, ActiveX would allow only 1 GUI component per .OCX (am i wrong here? is it possible to incorporate more that 1 control in an .OCX file?) and this would mean that i would have to distribute a lot of .OCX files and it would just not look right. Can you tell me if ActiveX is still considered a "modern" way of doing things? I wouldn't want to use something that is about to be deprecated. Thanks.
RefuseResist13 wrote:
is it possible to incorporate more that 1 control in an .OCX file?
Yes.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles