|
Good evening truly people,
With all due respect, may I know how HOW THE HELL do I get a node selected using the right mouse button and then show the context menu..
I'm trying this
private void tree_Level_MouseDown(object sender, MouseEventArgs e)
{
tree_Level1.GetChildAtPoint(tree_Level.PointToClient(new Point(e.X, e.Y)).Select();
}
Then I managed to show the context menu but once that happens, it goes back and selects the old node
Smile: A curve that can set a lot of things straight!
(\ /)
(O.o)
(><)
|
|
|
|
|
Use the AfterSelect event instead.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Hi Pete and thanks for the help.. Actually, it was already in the AfterSelect event and I had to move it to obtain the mouse location value form the passed arguments. If you tried to run the piece of code I just pasted, it will simply not work anywhere not just out of the AfterSelect event!
Smile: A curve that can set a lot of things straight!
(\ /)
(O.o)
(><)
|
|
|
|
|
In the NodeMouseClick event:
treeview.SelectedNode = treeview.GetNodeAt(e.Location);
|
|
|
|
|
Hey! Thanx a bunch buddy, that was a great help!
Smile: A curve that can set a lot of things straight!
(\ /)
(O.o)
(><)
|
|
|
|
|
|
Hi,
In my VS2005 Add-in i need the constructor and classname from a cs file. Now i run through all the lines of the file looking for a line containing "class" and not commented ofcours, but i was wondering if there is another way using the projectitem.document?
thx
Kurt
|
|
|
|
|
Just parse through them. Maybe use regular expressions 
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
I was just wondering,..
if the VS studio editor could recognize them and mark them with a color, maybe the functionality is available also on the projectitem.documents. So i guess the parsing already exists but how can we use them?
|
|
|
|
|
i know the meaning
now i implemented it in the project
using the following code
protected void Page_Load(object sender, EventArgs e)
{
Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Abandon();
foreach (string ste in Session.Keys)
{
Response.Write(ste + ":" + Session[ste]);
}
}
initially i used the two session variables.
if i use the session.clear()
it leave me with 0 session count
but the session vaiables remain the same if using the sesssion.abandon()
Sonia Gupta
Soniagupta1@yahoo.co.in
Yahoo messengerId-soniagupta1
Love is Friendship and Friendship is Love....
|
|
|
|
|
Session.Abandon lets you access the session variables until the page goes out of scope (e.g. you redirect the user to another page). Session.Clear removes the variables instantly.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Session.Abandon marks the Session object to be abandoned. When the current request is finished, the Session object will be removed, but it's available as long as the code is running. When the user makes another request, a new Session object will be created.
Session.Clear only removes the session variables from the current Session object. The Session object itself will not be removed.
---
single minded; short sighted; long gone;
|
|
|
|
|
i am using the following code
Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Clear();
it renders the Session["Sonia"] and session["Sonia1"] to null.
Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Abandon();
leaves the session["Sonia"] AND Session["Sonia"] AS IT IS.
Is this what u mean to say.
Sonia Gupta
Soniagupta1@yahoo.co.in
Yahoo messengerId-soniagupta1
Love is Friendship and Friendship is Love....
|
|
|
|
|
Sonia Gupta wrote: Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Abandon();
leaves the session["Sonia"] AND Session["Sonia"] AS IT IS.
Is this what u mean to say.
This is correct. Once you leave the scope of the request, Session["Sonia"] and Session["Sonia1"] will be removed, but until then you can still access these variables.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
but the fucntion session.clear() clears the session values not the session key.
here session.clear() clears the session key as well, y this is happening
Sonia Gupta
Soniagupta1@yahoo.co.in
Yahoo messengerId-soniagupta1
Love is Friendship and Friendship is Love....
|
|
|
|
|
Sonia Gupta wrote: but the fucntion session.clear() clears the session values not the session key.
No, it doesn't clear the values, it removes the items.
Sonia Gupta wrote: here session.clear() clears the session key as well, y this is happening
The Session.Keys collection is a collection of the names in the Session.Items collection. As Session.Clear removes all the items in Session.Items, the Session.Keys collection also becomes empty.
---
single minded; short sighted; long gone;
|
|
|
|
|
one thing i wanted to make clarification about is that
session.abandon() does not remove the key or the value until we navigate to another page.Once the use navigates to another page , both the key and the value gets removed.
and as far as the removing of session key and value is concerned , session.clear() method is sufficient , according to my understanding . Then What's the need of session.abandon()?
Sonia Gupta
Soniagupta1@yahoo.co.in
Yahoo messengerId-soniagupta1
Love is Friendship and Friendship is Love....
|
|
|
|
|
Suppose that you want to continue working with the session in the context of the page, but you want the session to be cleared when you leave the page. If your page hosts another page in an iframe, then the inner page also has access to the session variable. This means that you can abandon the variable in the Page_Load, and still access it in the inner page.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
session.abandon removes the key and the value. right?
Sonia Gupta
Soniagupta1@yahoo.co.in
Yahoo messengerId-soniagupta1
Love is Friendship and Friendship is Love....
|
|
|
|
|
Eventually yes.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
in, Session.Clear()
Session key also remove.
coz..
foreach (string ste in Session.Keys)
{
Response.Write(ste + ":" + Session[ste]);
Response.Write("
");
}
O/p is nothing.
Never Think That You Have Failed Instead Always Think That u hav Better Chance Next Time...
|
|
|
|
|
What does this have to do with Session.Abandon removing the keys?
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
in, Session.Clear()
Session key also remove.
coz..
foreach (string ste in Session.Keys)
{
Response.Write(ste + ":" + Session[ste]);
Response.Write("
");
}
O/p is nothing.
Never Think That You Have Failed Instead Always Think That u hav Better Chance Next Time...
|
|
|
|
|
Sonia Gupta wrote: session.abandon removes the key and the value. right?
No, it doesn't.
It marks the Session object for removal. When the request finishes, the entire Session object is removed. The items are never removed from the Session object.
---
single minded; short sighted; long gone;
|
|
|
|
|
Sonia Gupta wrote: i am using the following code
Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Clear();
it renders the Session["Sonia"] and session["Sonia1"] to null.
Actually, it removed the items. If it would just set the items to null, the Session.Count property would still return 2, but clearing the session items makes it return 0.
Sonia Gupta wrote: Session["Sonia"] = "11";
Session["Sonia1"] = "12";
Session.Abandon();
leaves the session["Sonia"] AND Session["Sonia"] AS IT IS.
Yes. The current session can't be removed until the current request is completed. That would be sawing off the branch you are sitting on.
---
single minded; short sighted; long gone;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
