|
Yep, that won't work. ManagementObject is outside the inheritence path of your class. Your class is a sister to ManagementObject.
Curious...why didn't you just inherit from ManagementObject in the first place?
|
|
|
|
|
I inherited from BaseObject, as the documentation says. It does not talk about anything else (except for events).
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
From the MSDN documentation:
Instrumented applications cannot expose writeable properties on new classes that are not wrappers of underlying unmanaged WMI classes.
A user of a class created by an instrumented application cannot change instance data and then write the data back using a Put operation.
I think I will have to create my classes using something else than the .NET way if I want to have writable properties. It seems to be the same for methods:
Managed code providers cannot define methods.
Yes, I tried using a method.
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
Yep. I found the same thing in several places. This is something new I didn't know and didn't expect given the documentation on the Management namespace.
It looks like you can only generate ReadOnly properties for a WMI class under .NET. How useless!
Sorry about the rest of the crap I gave you. Usually the coder misses something simple and doesn't realize it. They go 'round and 'round, and when they finally post the code, wallah! Something that could have been solved in 5 minutes. It's all too common.
|
|
|
|
|
Dave Kreskowiak wrote: Sorry about the rest of the crap I gave you. Usually the coder misses something simple and doesn't realize it. They go 'round and 'round, and when they finally post the code, wallah! Something that could have been solved in 5 minutes. It's all too common.
No hard feelings
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
You get my 5 for perseverance...
|
|
|
|
|
Moi, je te donne 1 pour ton incompréhension à comprendre le problème.
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
Le Centriste wrote: incompréhension à comprendre
|
|
|
|
|
Je voulais dire "incapacité". Mauvais choix de mots.
En passant, tu liras la fin du thread et tu comprendras pourquoi ce n'était pas nécessaire de poster le code complet.
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
For the umptiest time, no one asked for the complete code, just the relevant code.
BTW the majority of people in Belgium speak Dutch, not French.
(and most of them know French sufficiently to spot mistakes)
|
|
|
|
|
I thought most people in Belgium spoke Flemish...
-----
Formerly MP(2)
If atheism is a religion, then not collecting stamps is a hobby. -- Unknown
|
|
|
|
|
Hello,
I'm trying to get the mime type of a file like (application/msword)
that determine the application that will open this file and its extension but I can't do it in my windows app.I want to know how to get the type of a file and how to get the extension from this type.
Thanks.
Dad
|
|
|
|
|
If you are just trying to open the file up, use the following code and Windows will do the work for you with any registered mime type.
I use this to open up .PDF files saved in the database automatically.
System.Diagnostics.Process.Start(file name here);
Hogan
|
|
|
|
|
Great thanks,
but I want to send the mime type to a server that running a file net engine that require the mime type like we do in web apps by using the file upload control ,this is the first part the second is I want to get the extension when I get the file back from the server to write it to the client hard desk by its right extension.
I need help in this .
thanks.
Dad
|
|
|
|
|
I have a program that loads in a large image (14000x10000 pixels) & resizes the image to fit on the screen. Once it is resized I track the pixel that the mouse is over. This is reported back as the actual location on the screen (somwhere within the 1280x1024 of the screen resolution). I would like to know how to get the actual location within the larger image.
Any thoughts?
Thanks
R.Myers
|
|
|
|
|
Just multiply the coordinates with the same scale that you used to shrink the image.
---
single minded; short sighted; long gone;
|
|
|
|
|
If you select one pixel on your screen, the corresponding location on the original
image would be an entire rectangle with approx dimensions of 12*14; its location
can be found as Guffa already explained, as well as its exact size.
|
|
|
|
|
Thanks Luc & guffa.
I think that'll work. (It looks pretty obvious when you said it )
R.Myers
|
|
|
|
|
[I thought I had found my answer earler so I had deleted the other post, but I didn't.]
I am working with data where records are stored in big and little endian.
For example a file has:
16 fields some are intergers and some a doubles and half are stored in big
and the other half in little.
I know that my system should be in a little endian state but..
How do I convert from big to little and little to big?
God Bless,
Jason
DavidCrow wrote: It would not affect me or my family one iota. My wife and I are in charge of when the tv is on, and what it displays.
I do not need any external input for that.
|
|
|
|
|
The Windows Sockets library has built in functions or you could write your own using bitwise manipulations.
|
|
|
|
|
Hi,
I dont think mixing big-endian and little-endian data in a single file is a good idea.
If only one type of system is involved, convert the "wrong endian" data before storing
it; it different types of systems are involved, select one type, and let the systems
with the other convention do all the conversions every time.
Anyhow, you can change from one to the other with simple byte swapping
BTW the code is the same for either direction i.e. big2little and little2big
are no different.
The code can be based on byte extraction/insertion (using and, shift, or),
or on a union-like construct (using a struct with FieldOffsetAttribute).
|
|
|
|
|
Luc Pattyn wrote: I dont think mixing big-endian and little-endian data in a single file is a good idea.
I agree. The problem is that the data files are created by another applications and I don't think I will be able to change their think on the subject.
Anyways I think I figure out a to flip them.
Correct me if I'm wrong if you have a 32bit integer (int32) it has 4 bytes.
So we could say a int32 bytes like this WXYZ flip to ZYXW.
If that is correct then my method works just fine.
static byte[] FlipBytes(byte[] bArray)
{
byte[] bNewArray = new byte[bArray.Length];
int j = 0;
for (int i = bArray.Length - 1; i >= 0; i--)
{
bNewArray[j] = bArray[i];
j++;
}
return bNewArray;
}
God Bless,
Jason
DavidCrow wrote: It would not affect me or my family one iota. My wife and I are in charge of when the tv is on, and what it displays.
I do not need any external input for that.
|
|
|
|
|
Yes, that is correct.
And a good way if you start off with a byte array.
If you start off with a long, an int, a short then it would be a pitty to first
create a byte array.
BTW you may not need the new byte array, you could swap bytes in situ:
it suffices to loop over half of the bytes and swap them (using one temporary byte).
int lenMinus1=bArray.Length-1;
for (int i = 0; i <= lenMinus1/2; i++) {
int j=lenMinus1-i;
byte temp=bArray[i];
bArray[i]=bArray[j];
bArray[j]=temp;
|
|
|
|
|
Luc Pattyn wrote: Yes, that is correct.
Thanks I got one right
Luc Pattyn wrote: If you start off with a long, an int, a short then it would be a pitty to first
create a byte array.
Why would it be bad to create a byte array?
Luc Pattyn wrote: you could swap bytes in situ:
I think I might just do that.
Thanks for you input.
God Bless,
Jason
DavidCrow wrote: It would not affect me or my family one iota. My wife and I are in charge of when the tv is on, and what it displays.
I do not need any external input for that.
|
|
|
|
|
jason_lakewhitney wrote: Why would it be bad to create a byte array?
It is not bad, but why create and work with an object if there exists a simple
solution without such object.
Hence, if you start off with a byte array, operate on it; if you start off with
a long/int/short, operate on it. Example:
ushort val=0x1234;
val=EndianChanged(val);
...
public ushort EndianChanged(ushort val) {
return val=(val>>8) | (val<<8);
}
As you can guess, this method is much cheaper than the byte-array based solution,
it is less code and no new objects.
Of course, if you need this endian changing only a couple of times, it does not
matter how you do it. If you are going to read an entire binary program file,
maybe several MB in size, it may well matter.
r
|
|
|
|