|
Hi, all:
In VS2003, I had no problems declaring (custom control) properties that were visible in the properties window for the control - also in a catagory of my choosing (typically named after the control, itself).
With VS2008, I had to change the format for declaring the properties (to one much like that of C#). They compile without error, and can be used within the control class.
Problem is that they don't show in the properties window. Even if I use standard names. There also seems to be an insistance that I declare them as follows:
public:<br />
[Description("Some descriptive verbage"),Category("Layout"), Browsable(true)]
static property type propertyName {<br />
public: void set(type value) {...}<br />
public: type get() {....}<br />
}
The declaration as static has quite a few annoying side effects, and was unnecessary in the oldsyntax version (below).
This is not the first time I visited this problem, but now the frustration level is getting to me. How is this done correctly? I'd settle for, as above, where I have to use a predefine category, but would prefer to do as I'd done before, which is to block them together in a custom name.
Thanks, in advance,
Balboos
Old Syntax (VS2003):
<br />
public: <br />
[Description(S"Some Descriptive Verbage"),Category(S"Anything")]<br />
__property type get_PropertyName() { ... }<br />
__property void set_PropertyName(type value) { ... }
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
Never Mind - I finally Got it !
&U$A)U*$)P$*)P($ !!!!
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
...and what were you doing wrong or needed to change? This way the next person that runs in to the same problem has some ideas on what needs to be fixed.
Scott.
—In just two days, tomorrow will be yesterday.
—Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[ Forum Guidelines] [ Articles] [ Blog]
|
|
|
|
|
Fair Enough - The following will work, creating the properties and putting them in the specified category within the Properties Window for the control:
public:
[Description("Type A Description That Appears at Bottom of Prop Window"), Category("Some_Category")]
property type popertyName {
public: type get() { return dataMember;}
public: void set(type value) { dataMember = value; }
}
Now the above seems to be quite a simple change - the mess was that the early reference I found to this steered me in the direction of declaring the property static. All seemed well, although, being static, it require all of its members/called methods to be static objects, as well. This was not, for the general case, practical (and for inherited members, sanely do-able).
I figured out the error when I tried to use the property via 'hand coding': it would not let me use it as an instance, but only as a class member (because it was static - Duh!). This made me consider the static declaration not only a nusiance, but just plain wrong. Throwing caution to the wind, I deleted the (recommned via examples) static declaration and let the magic happen.
So trivial in hindsight. But why didn't the MSDN help just #*&)&&^)^ spell it out with a clear example?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
Thanks. Now that the difference is clear, it does seem so trivial. 
Balboos wrote: But why didn't the MSDN help just #*&)&&^)^ spell it out with a clear example?
You're joking, right? MSDN docs with clear examples? It'll never happen.
Scott.
—In just two days, tomorrow will be yesterday.
—Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[ Forum Guidelines] [ Articles] [ Blog]
|
|
|
|
|
Scott Dorman wrote: You're joking, right? MSDN docs with clear examples? It'll never happen
Either a rhetorical question or just being cynical.
When I was first learning managed C++, I was trying to find out how to use the ExecuteScaler() method from ADO.NET - I was having trouble figuring out how to cast the value in the new syntax. Foolishly got to the MSDN help, I found an example of ExecuteScale(), but they treated it like it had void for a return type (instead of Object * which was before the current Object ^). My initial instinct was to find out if homocide was illegal in Redmond, Washington.
Another rhetorical question, then: the people who have written the 'help' - are they sadists - or just plain stupid?
Yet . . . I keep ending up going back there . . . making me wonder about myself, or, to quote Forest Gump: "Stupid is as stupid does" ????
Thank the Great Coder In The Sky I only have half-a-day, today.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"How do you find out if you're unwanted if everyone you try to ask tells you to go away?" - Balboos HaGadol
|
|
|
|
|
Hi,
I want to give the XMLwrite::Create(...)
an URI format address...
because I want to save my file (e.g config file) in my http:// address. and I don't want to use Database...
If there is a way to do it(or other ways) please tell me
thank you.
Every new thing you learn,Gives you a new personality.
|
|
|
|
|
dSolariuM wrote: because I want to save my file (e.g config file) in my http:// address
HTTP doesn't work like that, you better do some studying. Software developers should understand the technologies they intend to use before planing how to use them, otherwise you end up trying to install a clutch in your refrigerator. 
led mike
|
|
|
|
|
There are Mdi parent and its child form. In parent Mdi header file I include "child.h" in order to create and show it to the screen. But how to access from child any public data of Mdi parent. If I include in child.h "parent.h" it does not compile? cross reference.
parent.h file
#include "child.h"
class Parent {
...
}
child.h file
#include "parent.h" <------- does not allow to be compiled
class Child {
...
}
chesnokov
|
|
|
|
|
Look at Model-View-Control pattern[^], views should not be tightly coupled. One obvious approach to avoiding two classes being tightly coupled is to use a third.
classA classB
\ /
\ /
\ /
classC
led mike
|
|
|
|
|
|
The manifest may only be part of the problem, if at all.
You also have to ensure all required modules/assemblies/etc.
are available on the target machine.
Deployment (C++)[^]
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
|
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
|
Thanks, but the problem was only solved when I used static linking instead of dynamic linking of multithreaded C library 
ARSALAN MALIK
|
|
|
|
|
Arsalan Malik wrote: the problem was only solved when I used static linking
In that case, you either deployed a debug build, or didn't install the CRT
libraries properly on the target machine.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
How to use an Object (like datagridview) in a thread?
I mean cross-thread operations...I tried to use CheckForIllegalCrossThreadCalls=false
but as MSDN says it is unsafe and also it dosn't run well...
|
|
|
|
|
Hi all
I am launching from my C++/Cli console application a child process using System::Diagnostics::Process class.
This child process throws an exception and the damned "do you wish to debug" window .
Is there any way to trap this kind of exception in my code?
Many Thanks
ManuStone
|
|
|
|
|
exceptions are a stack mechanism, a parent process has no access to a child process stack.
led mike
|
|
|
|
|
Hello,
I have a problem with a mixed mode dll. In this dll it is a class (#pragma unmanaged) which contains a singleton. But now I have a porblem during unloading the program. During unload the program I became allways the message "Unhandled exception at 0x7c812a5b in Test.exe: 0xC0020001: The string binding is invalid".
I have searched already a lot around the internet but there are a lot of messages regarding this problem. The most have only a solution for VS2003 and not VS2005. I have tested all what I have found.
It is really easy to reproduce this problem. You need only a mixed mode dll and a unmanaged class with an singleton (the problems happens also with automatic atexit registration and also in manual)
Best regards
Hansjörg
|
|
|
|
|
Have you tried freeing the Singleton prior to the process exiting?
led mike
|
|
|
|
|
How I should free the singleton prior to process exiting? It is freeing automatically and I don't wont an explicitly call to a function.
Best regards
Hansjörg
|
|
|
|
|
hansipet wrote: I don't wont an explicitly call to a function.
Just as a way of testing to see if it solves the problem, why not?
led mike
|
|
|
|
|
What is the ways to use vb and c# code in vc++.net application program? Thx.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
