is there a way to enhance .NET ListView control to capable to show two line items? I couldn't use third party libraries.
Thanx
There is no method to enhance the buil-in in list view control.
have you thought about creating a 'user control'? that for sure will allow you to dream up your own list view that would allow for multi line.
Regards
Related
I'm looking for ASP.NET TreeView drag and drop functionality without using a third party control. Can anyone guide me with JavaScript code?
This is not possible out of the box. Of course you could write your own drag & drop functionality, but the effort will be huge and you need to have very good JS and/or jQuery skills to do this.
I would prefer to using a third party JS/jQuery TreeView Control with Drag and Drop capabilities. So you will have less headache with using existing one also less error rate.
Successfully using the AJAX Control Toolkit AutoComplete extender, I'm looking for a Windows Forms 2.0 control that behaves similar to it:
Since I want to use the control to enter multiple e-mail receivers, my primary requirement is to have multiple, independent items to auto-complete.
I.e. this cannot be done by the standard auto complete feature of a TextBox control which only supports auto-completing one string.
In other words, I'm looking for something similar than Outlook's e-mail text box (but not as advanced, just the auto-complete part, no underlining required):
Even after searching Google (and Bing) for quite a long time I manage to have no luck in finding such a control.
My question:
Is there some example out there on how to build such a control, or even a finished control to use?
Since the application should be very slim, I do not want to use 3rd party libraries like DevExpress or Telerik or Infragistics.
Update 2014-12-24:
The commercial DevExpress library now has a Token Edit Control that might just be the control I was looking for:
You might take a look at the IAutoComplete interface. That will let you create a class that you can use instead of the standard auto-complete for an edit box. In that class you would handle what part of the string you are auto-completing on and the source of where the data is coming from.
http://msdn.microsoft.com/en-us/library/bb776292(v=VS.85).aspx
Windows Form (in C#) - I need to create a custom listbox control for the following requirement:
There is a listbox with a long list of items. I want the user to be able to click in the list, and then start typing and have it automatically take them to the matching item (I call this "type ahead"). It needs to be able to do this for as many characters as they type that have a match.
This control should be really reusable without much changes.
What are things/points I should keep in mind while developing a reusable custom control? (if you provide a good pattern as a sample... will be more helpful)
In Real World scenario the first decision should be buy vs build. if your application is a serious one and not just for hobby and there is budget for it I would check some of those great controls collections like DevExpress or Telerik for WinForms. You would need a grid as well at some point, eventually, and surely your custom or framework one cannot compete theirs.
I refer to those libraries because i believe they already have a listbox with autocomplete as you described in your requirements. check the online demos on their websites...
I want to use a treeview control in my asp.net project and when i drag and drop anything, it should update database. and there should be sort, when I change the sort when I drag and drop, the order column should be changed at the database.
(It is clear that treeview will get the items from database.)
I would search for examples of this via google to see what options are available with the standard .NET components, and 3rd party components (commercially purchased and jquery style plugins) See which one best fits your need and have a go at implemneting what you need. If you have further problems, let us know.
All in WPF:
Developing a wizard application, user has to answer a number of simple questions before brought to the main app. The main app is then prefilled with the information obtained from the wizard.
I started with a Window which I then planned to add usercontrols to. The main window would have the user control in the first row, then Next and Previous buttons to control moving between the controls in the second row. This way I could easily control the logic to switch between screens like:
WizardControl1.IsVisible = false;
WizardControl2.IsVisible = true;
But for some reason, user controls do not have setter for IsVisible. Hurray.
So then I thought I would just use seperate windows for each section of the wizard. The problem with this approach is that now when stepping between, the window opens in random positions, and by steppign through the wizard with next, the next window pops up randomly which is really distracting and frustrating.
So how can I develop a wizard properly? I don't get why this is so hard...not exactly rocket science... replacing text and controls and storing input after pressing next/previous!
Thanks
Check this link:
http://www.codeproject.com/KB/WPF/InternationalizedWizard.aspx
This is the article about building wizard in WPF by Josh Smith, it's seems to be nice pattern.
I found it's helpful for me, hope you'll too.
There is also an open source Avalon Wizard control on codeplex.
I'd probably aproach this using data binding and template selectors. Have the wizard form bind to a "WizardData" class, which exposes a list of "WizardPage" base classes.
The WizardData class can expose properties defining the correct info on the forms, and display a control for the main page that uses a template selector to determine the proper control to display based on the actual type of the particular wizard page.
It sounds like more work than it is, really. It also gives you the benefit of good separation between code and UI (all "work" is done by the WizardData and WizardPage classes), and the ability to test logic independent of the UI.
It's also a very WPF/MVVM way of approaching the problem.
I recognize this does not directly address your question, but I thought I'd mention it as a possible alternative. I've used Actipro's Wizard control with pretty good results, and when I have needed support, they have been very responsive. I am not affiliated with them in any way; I just like not having to write the plumbing to manage a wizard.
The property is called "Visibility".
I find that I do better when I dynamically add and removing controls rather than hide them.
I was looking for a Wizard solution too. I have the need to stick with stock WPF components so I implemented the wizard using a standard form and a tab control.
I only hide the tabs at runtime so there available in the IDE. At runtime just use Back, Next, Finish... to navigate thru the tab items
works good