Main > Software Forum
State of the FE devs?
Minwah:
--- Quote from: screaming on September 08, 2006, 11:12:13 pm --- Speaking of which, writing a config program is all well and good, and I had fun with it mostly because I learned just about everything possible about MAMEWAH - my FE of choice then. MAMEWAH ended up going a different direction than I had hoped, which caused my interest in maintaining the config program slim to none (okay, more like none). I gave up the source to the interested parties.
--- End quote ---
Just out of interest, what 'direction' did Mamewah take not to your liking? Really, little has changed since you made the config program...in fact no official releases yet since v1.61.
headkaze:
--- Quote from: youki on September 11, 2006, 04:23:36 am ---In C++ we could always find a way to fix that kind of problem because we have control.
--- End quote ---
Although a lot less likely you can still stumble upon bugs in the Windows APIs eg. TransparentBlt comes to mind.
There are limitations in .NET that I don't like, like some areas of controls and API support in the namespaces are missing. Like the Microsoft.DirectX.AudioVideoPlayback namespace was a lame attempt at wrapping the DirectShow API's.
I have to take my hat off to you though youki, you certainly have my respect for writing your FE in pure C++. It's by far the most difficult of the languages mentioned here to master and requires the most programming skill and discipline. You can afford to be alot more lazy on the newer languages although I try not to let it make me become a lazy coder ;)
Minwah:
--- Quote from: headkaze on September 11, 2006, 08:30:46 am ---There are limitations in .NET that I don't like, like some areas of controls and API support in the namespaces are missing. Like the Microsoft.DirectX.AudioVideoPlayback namespace was a lame attempt at wrapping the DirectShow API's.
--- End quote ---
JCrouse mentioned to me that control arrays are not possible in .net - that's put me off it for life :P
headkaze:
--- Quote from: Minwah on September 11, 2006, 08:44:34 am ---
--- Quote from: headkaze on September 11, 2006, 08:30:46 am ---There are limitations in .NET that I don't like, like some areas of controls and API support in the namespaces are missing. Like the Microsoft.DirectX.AudioVideoPlayback namespace was a lame attempt at wrapping the DirectShow API's.
--- End quote ---
JCrouse mentioned to me that control arrays are not possible in .net - that's put me off it for life :P
--- End quote ---
What do you mean no control arrays? For a start ArrayList is an array of any object you want, so say you have a Label and TextBox, you can add them to the same array.
--- Code: ---ArrayList myArray = new ArrayList();
myArray.Add(myLabel);
myArray.Add(myTextBox);
foreach(Control myControl in myArray)
{
MessageBox.Show(myControl.Name);
}
--- End code ---
Or you can have any control as an array Label[] myLabels; or Control[] myControls. So I don't know what JCrouse means when he says that, do you mean something else by control array? I havn't found any limitation in .NET in regards to arrays.
Howard_Casto:
That isn't the same thing.
With the old vs6 stuff you can do an array of controls, and put controls in an array. Now you can just put controls in an array.
The first is very useful for click events.
I can have an array of labels (label(0) to label(13)) and they share common events. So the same function can be called if any of them are clicked without any special code or for/case statements.
I haven't figured out how you can do that in .net, I think it's impossible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version