|
If you have a question then please edit the above and add it to your post. If this is your suggested improvement for Windows Explorer, then write an article or Tip and post it in the article submission section[^].
Use the best guess
|
|
|
|
|
This is C# *discussions* so I think it's ok if he doesn't have a question and is just looking for general advice. Right? Probably not gonna get it, but I think it's a valid post for this section, and shouldn't the "questions" really be going to the quick answers section or on Stack Overflow?
This is the kind of thing I'd love to see here, or anywhere really... code discussions and critique is much more fun than answering dumb questions.
|
|
|
|
|
Jasmine2501 wrote: This is C# *discussions* so I think it's ok if he doesn't have a question
Not according to http://www.codeproject.com/Messages/1278604/How-to-get-an-answer-to-your-question.aspx[^].
Jasmine2501 wrote: and shouldn't the "questions" really be going to the quick answers section or on Stack Overflow?
No.
Jasmine2501 wrote: This is the kind of thing I'd love to see here, or anywhere really... code discussions and critique is much more fun than answering dumb questions.
Then I suspect you are at the wrong place.
Use the best guess
|
|
|
|
|
Yeah I read that, but it doesn't really make sense to have a forum if that's what it is. QA is done on Stack Overflow. This site has no purpose if it doesn't allow discussion. I think it's a good post.
|
|
|
|
|
Jasmine2501 wrote: Yeah I read that, but it doesn't really make sense to have a forum if that's what it is.
Well it's been like that since Chris set it up, and everyone seems happy that it is. I don't think changing it now would go down well with the membership.
Use the best guess
|
|
|
|
|
But I take that as a "sticky" with just plain good advice. It doesn't say anywhere that "this is the only thing you're allowed to do here" it's just information about how to ask good questions. I've been here many years, and we used to have good discussions, back when Chris set it up, and everyone was happy, yes, you're right about that. I clicked on a tab that says "discussions" to get here. Should be orange at the top of the page right now.
|
|
|
|
|
Jasmine2501 wrote: I clicked on a tab that says "discussions" to get here. Should be orange at the top of the page right now.
Big deal, it is titled "discussions", but everyone (apart from you) seems to accept that it actually means question and answer type discussions about technical problems, in fact the readmes at the top make it reasonably clear what the forum is used for.
OK, you don't like that, so post a request in Bugs & Sugs, write a paper on it, or create a survey, because in a day or so this thread will disappear off the front page and be lost forever.
Use the best guess
|
|
|
|
|
I think that is because people don't care about learning and exploring, they just want someone else to do their job. I don't see anywhere that it's a rule.
|
|
|
|
|
Jasmine2501 wrote: I don't see anywhere that it's a rule.
You also don't see anyone supporting your view.
Use the best guess
|
|
|
|
|
Yes, the web site designers don't seem to be here.
|
|
|
|
|
I didn't mean them, they have far too much work to do. I meant the ordinary site members who spend their time reading and answering these questions.
Use the best guess
|
|
|
|
|
Perhaps there's a reason that the button at the top says "Ask a question", and the sticky notes at the top of the forum bang on about questions. Maybe the web site designers had some input there.
|
|
|
|
|
SO is not the only place you're allowed to do QA. It doesn't have a monopoly.
Jasmine2501 wrote: This site has no purpose if it doesn't allow discussion.
Errm, the articles are the main point of the site. Everything else has been added as a service to provide a lifeline to people with code difficulties. The right place to have posted this would have been as an article (well, more likely a tip/trick), and the discussion could have followed there. As it is, this will disappear off the front page in a couple of days, and in a couple of months people will have forgotten about it.
|
|
|
|
|
I meant the forum area. LOOK at the top of the page you are on right now. Does it not say "discussions" up there?
|
|
|
|
|
Given how long I have been an active contributor and question answerer here, I know full we'll what it says, and I also know what the purpose of the forums are for. You can capitalise whatever word you like, it still doesn't get away from the fact that these forums were always intended to be used for questions.
|
|
|
|
|
What is wrong with the built in search, and how will this be better???
I think when the app starts up, don't make the user 'select' a folder, just show a treeview of their hard drive automatically.
I think you need to create some classes to separate the interface logic from the searching (and this will allow multi-threading the interface later), but that discussion is not relevant without the answer to the first question.
|
|
|
|
|
If well built, preferably using MVS 2008, you should be able to select a directory by clicking on the "Browse" search button. When you click the search button, the directory tree of your hard drive would be displayed as "Browse For Folder" dialog box. Browse for a particular folder and click on the "Search Button". Then you can search for your preferred file type or all the files (using *.* for file type) in that directory. It is very seamless.
I want to be able to select and highlight a file based on the file name the user inputs in the "TextBoxSearch".
|
|
|
|
|
Do you want to search for the name of a file or for the content of a file?
|
|
|
|
|
I really intend to write an article about how the search feature of Windows Explorer can be improved. However, this post is meant to address the problem with locating and highlighting a file within the "ResultTextBox" using the "Find" button in the form.
I have made attempts with "select" method but still would not work.
|
|
|
|
|
Guys, this is quite simple I'm sure but I can't see the knockout punch leading to a solution. Without going into reasons but I'd like to send a right-click context menu message to a control. For example:
On a form, I've got a listbox, a button, and a context menu. I've set the listbox property to use the context menu. On the menu, I've added a few test items and I've added a messagebox to each one when selected. So, when I run the app, I can right-click on the listbox, select an item from the popup menu and yup, the messagebox is displayed. That's all fine.
Coming back to the button: I want to call SendMessage using the handle of the listbox. I'd like to send a right-click command, then select one of the menu items, blah-blah-blah. Getting the handle of the listbox isn't a problem but what is proving awkward is knowing what values I need to pass to SendMessage. I've got it declared as a dllimport and the usual declaration is
SendMessage(IntPtr hWnd, int wMsg, IntPtr wParam, IntPtr lParam);
What I can't find out is what values I need to pass into wMsg, wParam, and lParam.
There's a0x7B declaration defined in a previous CP question[^] which is associated with a context menu so perhaps that's what I need to use for the wMsg parameter. If that's the right message command to use does anyone know what I'd set the other two parameters to?
So, on one click I'd like to select say, the second menu item, elsewhere, perhaps select the fifth menu item. If I can get it to work on a simple test app I'll be able to apply it to our production app. Any help appreciated - as usual.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
You can send WM_RBUTTONDOWN (0x204) followed by WM_RBUTTONUP (0x205) to the handle of the listbox and that will display your context menu.
[DllImport("User32.dll")]
public static extern int SendMessage(IntPtr hWnd, int Msg, IntPtr wParam, IntPtr lParam);
public const int WM_RBUTTONDOWN = 0x204;
public const int WM_RBUTTONUP = 0x205;
SendMessage(listBox1.Handle, WM_RBUTTONDOWN, IntPtr.Zero, IntPtr.Zero);
SendMessage(listBox1.Handle, WM_RBUTTONUP, IntPtr.Zero, IntPtr.Zero);
Edit: References
WM_RBUTTONDOWN[^]
WM_RBUTTONUP[^]
modified 3-Jun-13 6:23am.
|
|
|
|
|
Dave,
Thanks for the snippet and I'm happy to report that the popup context menu is displayed. The final bit I need to do is to select one of the menu items in the displayed menu. It contains four selectable options like ABC, DEF, GHI, JKL. If I wanted to select say, GHI, using SendMessage do you know how I'd do that?
Is that where I'd used 0x7b (WM_CONTEXTMENU)? I did a SendMessage call using 0x7b after WM_RBUTTONUP and I used a few variations of values for wParam and lParam but nothing I tried allowed auto-selection of a menu item. Perhaps WM_CONTEXTMENU isn't the right message value to use?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
I'm not sure on selecting the menu item - I'll have a look and see if I can figure it.
The WM_CONTEXTMENU message "Notifies a window that the user clicked the right mouse button (right-clicked) in the window", so it's an information message rather than one that invokes an action if I'm interpreting it correctly: WM_CONTEXTMENU[^]
|
|
|
|
|
I was leaning in that direction myself. I placed a MessageBox before and after the call using WM_CONTEXTMENU and they're displayed okay but the call using WM_CONTEXTMENU appears to be completely mute.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
|
|
|
|
|
Is there any reason you need to do this using SendMessage as it looks like it's going to get quite complex.
If you can, in order of preference:
1. Just call the method that handles the MenuItem's Click directly
testToolStripMenuItem_Click(null, EventArgs.Empty);
2. use the MenuItem's index and call PerformClick()
int itemIndex = 0;
listBox1.ContextMenuStrip.Items[itemIndex].PerformClick();
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
