TreeView node right-clicked is not the "selected" node... - C# Discussion Boards

Re: TreeView node right-clicked is not the "selected" node...

5-Jun-02 10:43

Why is it that when I right click on a tree node and my context menu pops up, the item that is returned by the treeView1.SelectedNode property is not the item that was right-clicked on, but whatever tree node happend to be selected before the right click?

i.e.

Folders
_________
|FolderA| <-- Currently selected tree node
---------
FolderB
FolderC <-- Right click here

treeView1.SelectedNode returns FolderA, not FolderC, even thought the selected node highlighting box temporarily moved to FolderC.

Scratching my head...

Thanks,
Rick

James T. Johnson5-Jun-02 11:07

Re: TreeView node right-clicked is not the "selected" node...

5-Jun-02 11:07

Thats just the way the TreeView works. Crappy answer, but if you look at the behavior in Windows Explorer it is the same.

I believe the justification is that selecting the node is so you can tell which node was right-clicked on. Right clicking should not select an item; you are merely requesting a menu to popup.

James

rhoward5-Jun-02 11:35

Re: TreeView node right-clicked is not the "selected" node...

5-Jun-02 11:35

I have to disagree, at least w/respect to how Windows Explorer works. If I left click Folder "A" in explorer to select it, then right click on folder "B" and select "properties" I get a property page for folder "B", not folder "A".

This is the behaviour on Windows 2000.

If I were programming with pure Win32, I would just do a hit-test on the item under the mouse cursor, but I can't find an analog in C#.NET.

Thanks,
Rick

James T. Johnson5-Jun-02 12:39

Re: TreeView node right-clicked is not the "selected" node...

5-Jun-02 12:39

rhoward wrote:
If I left click Folder "A" in explorer to select it, then right click on folder "B" and select "properties" I get a property page for folder "B", not folder "A".

Correct, but when you close the property page the folder "B" *isn't* selected, folder "A" is. Sorry I didn't make that clear in my posting.

James

rhoward5-Jun-02 13:50

Re: TreeView node right-clicked is not the "selected" node...

5-Jun-02 13:50

Sorry for the misunderstanding. You are definitely correct about "A" still being selected.

The point I was making is that Explorer displays properties for "B", not "A", which is what I was trying to achieve.

Thanks,
Rick

David Wengier5-Jun-02 11:31

David Wengier

5-Jun-02 11:31

As James said, that is by design. The way to work around the design is like so:

treeView1.SelectedNode = treeView1.GetNodeAt(e.X, e.Y);

Call that before you pop-up the context menu

--
David Wengier

Sonork ID: 100.14177 - Ch00k

Re: SOLVED - TreeView node right-clicked is not the "selected" node...

rhoward5-Jun-02 11:45

Repository controls not redrawing -tough one

5-Jun-02 11:45

Many thanks, David.

I was able to use GetNodeAt() in the MouseUp event for the tree to reset the selected node to the proper item.

Thanks again,
Rick

5-Jun-02 7:01

I have component object that handles controls in a typesafe array like so

<br />
[Designer(typeof(ComponentGen.Repository.CompGenDesigner))]<br />
public class CompGen : System.ComponentModel.Component<br />
{<br />
/// The collection of controls this repository component will handle.<br />
private ComponentGen.Collections.CtrlCollection c_ctrls = null;<br />
...<br />
}<br />

when the controls are added to the component using the design wizard, the form's Initialize() event adds this code:

<br />
this.compGen1.RepositoryControls.AddRange(new System.Windows.Forms.Control[] { this.MASTER, this.CATEGORY, this.TEST_CODE});<br />
...<br />
<br />
			this.Controls.AddRange(new System.Windows.Forms.Control[] { this.MASTER, this.CATEGORY, this.TEST_CODE});<br />
...<br />

*MASTER, CATEGORY, and TEST_CODE are the generated controls (System...Control wrapped controls)

The problem
when the controls are first drawn, they show up perfectly drawn. when the form is closed and re-opened, the controls are not redrawn (transparent) but still exist and work perfectly when run.

The problem goes away when the controls are not added to the repository in that Initialize code.

Questions, Leads
-Do i have to override a paint or something in either the controls designer or the repository component?
-Why is simply adding references to the components in a collection stopping the form from repainting the controls?

comon now, lets see a little effort

5-Jun-02 11:48

This is a good question and im surprized ive got nothing so far. but right clicking on a tree gets four replies in an hour! come now. where have all the gurus gone?

Re: Repository controls not redrawing -tough one

James T. Johnson5-Jun-02 12:36

Re: Repository controls not redrawing -tough one

5-Jun-02 12:36

poodull wrote:
Do i have to override a paint or something in either the controls designer or the repository component?

Are MASTER, CATEGORY, and TEST_CODE controls of your own design or ones provided elsewhere?

Now my second question; what do you mean by a repository component? To me that would be a component which stores other components for later use; is that correct?

poodull wrote:
Why is simply adding references to the components in a collection stopping the form from repainting the controls?

Ensure that the Parent property is set to the proper entity, ie if the controls should be on the form Form1, Parent should be a reference to Form1.

James

6-Jun-02 6:14

James T. Johnson wrote:
Are MASTER, CATEGORY, and TEST_CODE controls of your own design or ones provided elsewhere?
MASTER, CATEGORY, and TEST_CODE are extended System...Controls I built. They have their own designer which i built, but really only adds a verb.

James T. Johnson wrote:
Now my second question; what do you mean by a repository component? To me that would be a component which stores other components for later use; is that correct?
Its a UI-less component which reads xml and creates these wrapped controls on the form using it's(the component) own designer. the designer also adds the controls to the component's public arraylist of controls.

James T. Johnson wrote:
Ensure that the Parent property is set to the proper entity, ie if the controls should be on the form Form1, Parent should be a reference to Form1.
The parent object does reference Form1. during design and runtime.

btw, thanks for the reponse.

Answered. if anyone reads this far

7-Jun-02 6:22

already kicked to the second page.. oh well...

the answer was that i was overriding OnVisibleChanged() for no reason and not doing anything about it. which would make all the contained controls in my generated controls disappear.

so, im an idiot, but im still shocked i didnt get more prods on this one.

thanks james

Preserving thumbnail metadata

dsweet5-Jun-02 6:14

dsweet

5-Jun-02 6:14

If I examine the propertyItems of a jpg file that was created using my digital camera I see that there is thumbnail related metadata. I have not been able to preserve the thumbnail data when using Image.Save(). Some metadata is preserved, but the thumbnail data is lost. Does anyone know what it takes to preserve the thumbnail metadata?

David

James T. Johnson5-Jun-02 12:59

5-Jun-02 12:59

Could you e-mail such a jpg to me?

I can only guess without one.

James

dsweet6-Jun-02 5:22

dsweet

6-Jun-02 5:22

I emailed one to you this morning.
Let me know what you find.
Thanks. Smile | :)

James T. Johnson6-Jun-02 5:20

6-Jun-02 5:20

Yep, I got it this morning; I was very busy up until a few minutes ago so I just started looking in to it.

James

James T. Johnson6-Jun-02 5:50

6-Jun-02 5:50

I'm not getting that behavior at all.

If I open the image then save it the thumbnail data is preserved.

Just a guess, but perhaps some operation you are performing is creating a new image; and when you save the jpg it creates the other metadata; but not the thumbnail.

James