|
Haven't dealt with it much in C#, but with all of the VB text boxes I've worked with, it works even without the ScrollToCaret() or SetFocus() thing.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Yeah, I never saw the method TextBox.AppendText() untill I was writing the first post, i was using the TextBox.Text += "", and the .Net Class Library says those 2 ways are the same. However, += does not advance the scroll bar, but AppendText() does. You must be using the method AppendText() then (but im not familiar with VB). Thanks for the reply though.
|
|
|
|
|
You do have to set the caret position, though.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
OK, I hvae a class Foo that holds a Brush.
Since Brush holds an unmanaged resource and implements IDisposable, I guess Foo has to implement IDisposable as well.
However, I'm still mixed up about Dispose, Finalize, and the recommended Dispose(bool disposing).
What's the "true" method to do here? Just
class Foo : IDisposable
{
protected Brush m_brush = null;
Dispose()
{
m_brush.Dispose();
m_brush=null;
};
} or is there more to it=
I know someday I'll get it 
TIA
(Just today I found an article that explaiend it nicely - but it's poof! gone..)
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
Ok, here's my understanding of it:
The Dispose method should be used to explicitly free up any internal resources, especially unmanaged ones such as handles etc. However, as far as I remember you should also call the Dispose method of an inherited class (if you have done so.
One other thing (although this is the big I'm shaky on -- haven't been doing this for a while now  ), you may also be able to suppress any additional GC finalisation. To do this, the GC class has a SuppressFinalisation method or something. This is the bit I'd check up on in the docs, but as far as I know you seem fine.
However, I also think that its important for calling code to call your Dispose method. Of course, this then means making sure that should an exception be thrown, the Dispose method is still called. Consequently, you'll want to add a call to Dispose in the finally{} block.
In C#, you may also want to check out the using() keyword, but I don't use it that often, I find it easier to read if I explicitly call Dispose where necessary -- which kinda makes me think decent commenting/documenting is a good idea, which of course I abide by 
--
Paul
"Put the key of despair into the lock of apathy. Turn the knob of mediocrity slowly and open the gates of despondency - welcome to a day in the average office."
- David Brent, from "The Office"
MS Messenger: paul@oobaloo.co.uk
|
|
|
|
|
peterchen wrote:
However, I'm still mixed up about Dispose, Finalize, and the recommended Dispose(bool disposing).
Finalize is the closest equivalent to C++ destructors that .NET has. The difference is that in .NET you can only clean up ValueType-based variables, in other words, IntPtr's that represent handles for P/Invoke use. This is because there is no guarantee on the order in which reference based (ie non-value types) will be Finalized.
That isn't very helpful in the long run, so the IDisposable interface came about so you could free up your managed resources. For example, flush a FileStream then close it. Because the FileStream uses a managed byte array to buffer the data you cannot use that byte array within the Finalize method. Sticky sticky.
Now to get to your question 
When Finalize is called we know we can only deal with unmanaged resources, but when Dispose is called we can deal with both. Rather than have two places to dispose of unmanaged resources MS came up with another pattern to use, this time it is a protected method that takes a bool.
protected void Dispose(bool disposing)
Both Finalize and the public Dispose methods should call this method to do the dirty work work. The bool tells if you can dispose of managed resources (ie Dispose was called). If it is false then you should only get rid of unmanaged resources.
Now to tie it all together:
class MyClass : IDisposable
{
Brush myBrush;
IntPtr myHandle;
...
~MyClass
{
Dispose(false);
}
public void Dispose()
{
Dispose(true);
GC.SuppressFinalize(this);
}
protected void Dispose(bool disposing)
{
if( disposing )
{
if( myBrush != null )
myBrush.Dispose();
myBrush = null;
}
FreeSuppaHandle(myHandle);
}
}HTH,
James
"It is self repeating, of unknown pattern"
Data - Star Trek: The Next Generation
|
|
|
|
|
Hi,
How (or how much) does the .NET framework support editing the properties of a class?
I have a class which contains and manages a "color scheme" (i.e. mostly Colors and Fonts), and would like to allow the user editing it in a property list.
is there something already provided? Can I "plug in" the editing of a custom class? Or do I have to do it on my own?
TIA
Peter
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
is there something already provided?
There is the Property Grid, which is the same control VS.NET uses. For some reason they don't have it show on the toolbox by default, just right click on it then choose Customize Toolbox then select the proprty grid.
Then you can drag and drop the control like any other.
James
"It is self repeating, of unknown pattern"
Data - Star Trek: The Next Generation
|
|
|
|
|
Thanks - found it!
Figuring out how to use is a nice task for tomorrow...
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
I have a strange question:
In .NET, is it still standard to prefix a class with "c" and an interface with "i" like has always been done with C++ and VB?
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
No, and it was never standard to do that in any language that I can think of.
|
|
|
|
|
For instance, IPersist, IViewObject2, etc. and CCosmoDoc, CPages, etc. I know it is standard to prepend an "I" to the name of an interface. It was always standard in certain instances to pre-pend classes with a "C".
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
jdunlap wrote:
In .NET, is it still standard to prefix a class with "c" and an interface with "i"
Classes don't have a prefix, but the prefix on interfaces has stuck around. I presume to make them stand apart from other datatypes.
James
"It is self repeating, of unknown pattern"
Data - Star Trek: The Next Generation
|
|
|
|
|
I already knew that I was still prefixed to interfaces, so I don't know why I lumped it in with the Class prefix thing.  After reading the article mentioned below, I agree that prefixing classes with a "C" is futile.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Check out this page[^] I came across yesterday.
|
|
|
|
|
  Good article though. I follow those conventions except for the "underscore on the end of class-level variables" thing. For class-level variables, I do m_varname
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi
|
|
|
|
|
Is there a utility that will take a win32 executable and generate a P/Invoke wrapper class for all the function that it exports.
|
|
|
|
|
The basic answer is no.
Imagine a tool that would do just that. Unless all functions pass and return trivial parameter types like int and char*, tell me how this tool manages to wrap the structures, classes, or whatever might be mangled in the exported functions without knowing their declarations ?
My recommendation is to use MC++ mix mode instead. That is write a wrapper library which does internally all native calls, and don't need marshaling. A bit overkill though if you only need a few interop to be done.
[edit]I have an url[^] for you.[/edit]
|
|
|
|
|
Yeah, I understand that you can't do functions that return custom parameters.
I just wan't to do the basic ones, like you said - the ones that return string, int, intptr, bool, etc.. I know that there are tools that make a list of exports. It shouldn't be that hard to take a list of exports and make the p/invoke code.
|
|
|
|
|
AK wrote:
It shouldn't be that hard to take a list of exports and make the p/invoke code.
I disagree. Suppose one of C/C++ parameters is LPSTR. How does the converter know that's an input parameter (C# string), or output parameter (C# out string). Another example, many functions in the WIN32 API use two parameters to allow to pass a fix-size LPSTR string along with the max size of it. You know this got to be translated using C# stringbuilder. Again how does the converter knows it ?
I could go on for years, especially if you get me started on marshaling issues, which add noise to it.
The only thing I see is the equivalent of the WIN32 API viewer, that tiny tool provided by MS in their site and which allows to interactively browse the WIN32API.txt file. May be someone is bold enough to write a WIN32API.csharp.txt will all premarshaled stuff in it. Here is an entry point[^].
|
|
|
|
|
System.IO.Stream sound_stream = new MemoryStream(buffer);
DirectSound.Buffer k = new DirectSound.Buffer sound_stream,applicationDevice);
--------------
Well, the buffer is a byte[] that I record from DirectSoundCapture , Now I want to play this byte[] , I study MSDN know that I should create a Stream
and write buffer in . Then create a SecondaryBuffer to play this Stream , my code is above , but it shows a error such that :
An unhandled exception of type 'System.ArgumentException' occurred in microsoft.directx.directsound.dll
Additional information: Value does not fall within the expected range.
I can't solve this problem , can anyone help me ???
Of course , I can write buffer into file and then open it , but I don't want
to waste time to do this process , I want to play sound form the buffer directly .
If you have a solution or can't understand about my post , please mail to me
j741119@Ethome.net.tw
Thank you for reading this bad grammar article  .
I am Craze JmmJ !!! A student from Taiwan who are instrest in Programming.
|
|
|
|
|
JmmJ wrote:
System.IO.Stream sound_stream = new MemoryStream(buffer);
DirectSound.Buffer k = new DirectSound.Buffer sound_stream,applicationDevice);
System.IO.Stream sound_stream = new MemoryStream(buffer);
DirectSound.Buffer k = new DirectSound.Buffer<big>(</big> sound_stream,applicationDevice);
I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02
|
|
|
|
|
I knew that post would catch you. 
|
|
|
|
|
.S.Rod. wrote:
I knew that post would catch you.
Yeah, nothin escapes the Code Police 
I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02
|
|
|
|
|
OHHHH......... What a terrible bug it is . @@
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
