|
The main thing to record is the URLs you follow. If the method is "POST", you should also record the data you sent to the server.
|
|
|
|
|
Yes, I'd like to record URLs I visited, but also to record all actions I do in these URLs, so if I write on a Form and press a Button I'd like to capture these information to replicate them later.
When I write my code where can I attach on it to grab such informations?
Is possible to have some c# code examples or links to better understand the way I have to follow?
Thank you very much,
Pietro
|
|
|
|
|
Good one,
So for every action on the page, you want to capture and store some where for further checking?
|
|
|
|
|
Yes, any advice?
I don't know how can I do it.
Pietro
|
|
|
|
|
I think you will need to write a browser plugin to capture things that are going on within a page. If you want to use the WebBrowser then it would have to be an IE plugin, if those even get loaded when you run the OCX version.
|
|
|
|
|
Why do you think plugin are better? Does their capabilities best fit my application? Now I'reading some documents on plugins. What features have I to study regarding my target?
Thank you for all,
Pietro
|
|
|
|
|
As far as I know the browser (including the WebBrowser control) doesn't expose the API you need to capture most things that the user does, so to get that you'd have to use something inside the browser, i.e. a plugin.
|
|
|
|
|
Can you show me some web link or other sources I can use to begin my work?
Thank you,
Pietro
|
|
|
|
|
Sorry, I've never done any plugin work with IE. I'd just be Googling and you can do that just as efficiently.
|
|
|
|
|
Hello again, CP! I am now trying to create a custom Form by painting a new title bar. I have never done this before but I did remember seeing it a lot when I was heavy into C++ and MFC. So I knew to look for WM_NCPAINT. The resources I found were telling me to override WndProc for the form and catch WM_NCPAINT, and then do my custom drawing from there. So this is what I did:
protected override void WndProc(ref Message m)
{
IntPtr hdc = GetWindowDC(m.HWnd);
Graphics g = null;
if ((int)hdc != 0)
g = Graphics.FromHdc(hdc);
if (m.Msg == WM_NCPAINT || m.Msg == WM_NCACTIVATE || m.Msg == WM_SETTEXT)
{
if ((int)hdc != 0)
{
OnNcPaint(g);
ReleaseDC(m.HWnd, hdc);
m.Result = (IntPtr)1;
}
}
else
base.WndProc(ref m);
}
In OnNcPaint(Graphics) I make a simple call to graphics.FillRectangle, which fills the entire rectangle with a solid color (in this case, Color.Blue). However, when I resize the form I am seeing a large amount of flickering across the entire form. The background is not custom painted. I have ResizeRedraw set in the form's "SetStyle()" method. When I remove ResizeRedraw it does not paint properly at all.
How can I eliminate the flicker here? This is kind of irritating. Haha. 
BTW, I have "base.WndProc(ref m);" in the "else" statement because otherwise, if I call it alongside WM_NCPAINT, it will just paint Windows' non-client area (Win7, Aero Theme). Thanks in advance.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
Hi,
I see two problems:
1.
the WndProc method is called quite often since Windows sends messages all the time, e.g. when you move the mouse over your form; so you should make it as lightweight as possible. And you didn't: you are creating the graphics object g whether you will use it or not. Now creating a Graphics is expensive, so this is slowing your form down, its responsiveness is not going to be what it could and should be.
2.
The Graphics object, when you created and used it but no longer need it, should be disposed of. So you should add something like if (g!=null) g.Dispose(); or just g.Dispose(); at some appropriate location inside WndProc (I guess just before calling releaseDC would be right, assuming you put FromHdc right in front of OnNcPaint). Failing to do so will enlarge your app's memory footprint and make the job of the garbage collector somewhat larger too.
BTW: this is true for most every instance you create when the class offers a public Dispose() method; the sequence ought to be: create-use-dispose. And the bigger the object, the more reason not to forget this. Note: there is a using statement that often comes in handy here.
|
|
|
|
|
Ah, yes. I do tend to forget quite often to call Dispose() on objects which support it. I have been making it a habit though, I am getting better. But that did not fix the flicker. 
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
you did postpone and hence reduce the number of FromHdc calls, as I suggested?
if so, is this actual code, or did you leave out some bits? you might choose to show the latest code again.
and what is inside OnNcPaint itself, that could be expensive (i.e. unnecessarily slow) too.
Now what exactly is flickering? the content of the form? the NC area?
You may have to look into the clearing of those areas, i.e. EraseBackground and such.
PS: I'll soon be off-line.
|
|
|
|
|
I did fix that as you suggested. And the flickering seems to be just a bit less, though nowhere near "reasonable" so to speak.
I actually have a lot going on in OnNcPaint. However, even if I remove everything and add a simple FillRectangle() for the caption/title area BY ITSELF, I still get the same flicker, except ONLY in the title area which is being drawn. It only flickers wherever I tell it to draw. So it definitely has something to do with the way it is drawing, not necessarily an expensive operation.
I am willing to take time on this. I have several custom controls which I am pleased with how they turned out. I figured Forms would be much more of a pain anyhow, haha. But I would sure love to figure it out.
djj55: Nice but may have a permission problem
Pete O'Hanlon: He has my permission to run it.
|
|
|
|
|
Hi,
without knowing much more on your exact situation, this is all I can tell you about the subject:
1. some flickering is unavoidable; the annoyance of flickering is proportional to the time it takes from the start of EraseBackGround to the end of Paint itself, and inversionally proportional to the frequency of your Paint calls. That is why shortening EraseBackGround and/or Paint is beneficial.
2. you can use double-buffering, where an unseen bitmap is operated on, and when ready the area is bitblitted to the screen (this doesn't require an EraseBackGround); either organize that yourself, or have the Control (or Form) do it for you.
3. there are a number of articles on OnNcPaint here at CP; I suggest you use CP search to locate and then read some of them.
|
|
|
|
|
I am not sure if this helps; I used to suppress the OnPaintBackground method in such scenarios
You can try some thing like
protected override void OnPaintBackground(PaintEventArgs pevent)
{
}
"Never put off until run time what you can do at compile time."
- David Gries, in "Compiler Construction for Digital Computers", circa 1969.
|
|
|
|
|
I want to use switch statement in windows form application how to use switch statement through buttons and textboxes ?
am stuck in this code please somebody help me and correct it namespace a
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void textBox1_TextChanged(object sender, EventArgs e)
{
string s;
s = textBox1(textBox1.Text);
}
private void button1_Click(object sender, EventArgs e)
{
string s;
textBox1("1","2");
switch(s)
{
case "1":
{ Form2 f = new Form2();
f.Show();
}
}
}
}
}
|
|
|
|
|
|
i actually want that whatever user enters in the textbox and when click on the enter buttn , i must open the next forms , let suppose if the user enters "1" it must open the form 2, similarly if he enters "2" it should open form 3
|
|
|
|
|
|
thanx alot , and what is the purpose of combo box ?
|
|
|
|
|
|
could u please give me /provide me the correct version ? i would be really thankful to you .
|
|
|
|
|
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}
private void comboBox1_SelectedIndexChanged(object sender, EventArgs e)
{
string s;
s=comboBox1.SelectedItem;
switch(s)
{
case "1":
Form2 f=new Form2();
f.Show();
break;
case"2":
Form3 a=new Form3();
a.Show();
break;
}
}
}
}
its giving me some error
|
|
|
|
|
Having read your original code, and the dialog between you and Colin (and admired Colin's patient responses), I want to offer you what I hope you will experience as constructive advice:
I believe you need to get a good book on C#, and really review the basics of the language Types, and, in WinForms, review the various common controls, like ComboBox, etc.
I'd suggest either the latest version of Jesse Liberty's 'Programming C#' (O'Reilly), and, for WinForms, I'd recommend the 2004 edition of Matthew MacDonald's "Pro .NET 2.0 Windows Forms and Custom Controls in C#" (APress) since I think Matthew has a certain "genius" for teaching and building slowly from fundamental concepts. There are, of course, other books on WinForms from Chris Sells (Addison-Wesley), Erik Brown (Manning).
In asking questions on CP, I'd suggest you begin the question with a clear statement of the context you are working in (WinForms ? WPF ? ASP.NET ?), and then a clear statement of what your goal is.
This goal statement can be very general: like: "I want to have a way at run-time in my WinForms application to select a certain type of Form to be created and shown."
best, Bill
"Last year I went fishing with Salvador Dali. He was using a dotted
line. He caught every other fish." Steven Wright
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
