|
Never post your email address in any forum, unless you really like spam! If anyone replies to you, you will receive an email to let you know.
Edit your question and remove the email address.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
|
Let me get this straight. You want to know if anybody here has worked on the video conference system you are building?
This is not the age of reason, this is the age of flummery, and the day of the devious approach. Reason’s gone into the backrooms where it works to devise means by which people can be induced to emote in the desired direction.
|
|
|
|
|
yup.. if somebody has worked on this type of project then let me know its basics and available api's.
|
|
|
|
|
I doubt seriously that anyone here is going to hand over that much code without being paid for it. Google may be your friend.
However, if you try it yourself, and have a difficulty, I'm sure someone here can help you through it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
This link[^] might help you.
you can also go there[^] having same problem with solutions.
|
|
|
|
|
how can convert image to webp format ?
|
|
|
|
|
Two choices. You're either going to have to write the whole image decoder yourself, or you can use the converter available here[^]. And before you ask, no I can't provide the code for you - you'd have to write it yourself.
|
|
|
|
|
You are really just no fun, Pete...
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Do you think my telling him is likely to stop him asking? It's more fun to be snarky when you've already told them. The moral high ground is a great place to live.
|
|
|
|
|
Bastard!
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
From you John, I take that as a compliment of the highest order
|
|
|
|
|
I think the mere fact that I'm handing out such obvious compliments might suggest that I'm getting soft in my old age.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Go out and shoot a hippy. That should restore things to the natural order.
|
|
|
|
|
|
This link[^] might help you.
|
|
|
|
|
Hi,
I know I posted a similar question a couple of days ago and I'm sorry about that but i'm going crazy about this problem...
So I will simplify the scenario.
I am developing a plugin system for a windows service application.
The plugin system has been developed with the AppDomain paradigm. I won't get into details of how my system works, but will demonstrate in a simple code example (of which I tried
namespace Foo
{
[Serializable]
public class Foo
{
Thread workThread_;
public void Initialize()
{
workThread_ = new Thread(new ThreadStart(DoWork));
workThread_.Start();
}
public void DoWork()
{
int i = 0;
while (i < 500)
i++;
throw new Exception("Unhandled exception");
}
}
}
namespace AppDomainTest
{
public class Bar
{
AppDomain new_domain;
public Bar()
{
}
private void new_domain_UnhandledException(object sender, UnhandledExceptionEventArgs e)
{
new_domain = null;
}
public void InitializeBar()
{
Foo.Foo foo_test;
new_domain = AppDomain.CreateDomain("Auxilary domain");
foo_test = (Foo.Foo)new_domain.CreateInstanceFromAndUnwrap("Foo.dll", "Foo.Foo");
new_domain.UnhandledException += new UnhandledExceptionEventHandler(new_domain_UnhandledException);
foo_test.Initialize();
}
}
}
I kept reading about AppDomains and how they are great for plugins and isolation and stability etc... but when the plugin has UnhandledException the whole application crashes with its main AppDomain crashing...
In my case a plugin can spawn multiple threads to do its work and those threads never interact with the core system, only through raising plugin events...
So my question is how to really protect from plugin failures (Unhandled Exception), so when 1 plugin crashes the rest of the application remains intact (continues to run) bearing in mind that a plugin can spawn multiple threads to do its work?
Thank you!
See the world in a grain of sand...
|
|
|
|
|
This is exactly what AppDomain.UnhandledException is for, I thought. This post surprises me.
|
|
|
|
|
BobJanova wrote: This post surprises me.
Pretty soon, that will stop happening.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Yes, I thought that also... but surprise surprise... damned M$ pulled a fast one...
But I can't accept that there is no other way to do this in .NET?
Which means that AppDomain is actually quite useless if this does not work... I don't see the point of AppDomains if you can't create a plugin system... this is very confusing...
Any other ideas?
See the world in a grain of sand...
|
|
|
|
|
DataGridView's SelectionChanged Event Fire earlier than CellDoubleClick Event.
But I hope SelectionChanged after CellDoubleClick.
My Program require:
1> DoubleClick any part of the row, this row selected=true.
read a value from this row as parameter order to open a dialog for do something.
2> When SelectionChanged, another controls's value will changed from the new selected row.
But if DoubleClick fired that another controls's value need not change.
How to do?
Thanks.
|
|
|
|
|
WinForm Controls often fire more events than you would expect.
Maybe SelectionChanged fires more than once, say first to indicate a possible previous selection is no longer selected, then to tell you something new is selected. And some other events may be present in between.
Suggestion: Add some logging to your event handlers to see what happens in sufficient detail.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Maybe not use DoubleClick and SelectionChanged?
Use MouseDown, instead, and test for how many clicks?
if (e.Button == MouseButtons.Left)
{
if (e.Clicks == 1)
{
DoSelectionstuff();
}
else if (e.Clicks == 2)
{
DoDoubleclickStuff();
}
Might not work... But you can set a flag in the MouseDown event indicating whether it was a 1 or a 2 click, then process your SelectionChange code appropriately.
|
|
|
|
|
|
Really? Not in my app. I had to use it to prevent row selection on doubleclicks. Hmm.
|
|
|
|