|
You can create a serialize class and encapsualte your class there and store your data in a XML file,for working with XML there are lots of projects in this site. Or if you do not want to store it in a XML,you can store that class in dat file.
Mazy
No sig. available now.
|
|
|
|
|
1) You can use a ListView instead of the ListBox, and store the path (B) in the .Tag property of each ListViewEntry. When you click a name (A), you can read the path from the Tag property:
for(int n=0; n
|
|
|
|
|
I have a windows application which has a lot of controls placed all over the screen. I have developed it in screen resolution of 1024 X 768.
The problem is that when the resolution becomes more, the controls occupy lesser space on the screen with lot of free area. If the resolution decreases, each control requires more space on the screen and many controls go out of the screen with scroll bars being displayed.
Is there a way of dynamically resizing the form controls based on the resolution of Windows?
Koos
|
|
|
|
|
First: There are many applications that they fir for one resolution and warn it before run. But beyond that after your InitializeComponent() add a method that set the methods based on this resolution. You can get the resolution with SystemInformation.VirtualScreen property,and every control has its own Size property.
Mazy
No sig. available now.
|
|
|
|
|
In addition to what Mazdak was talking about, you can also make use of the Dock property that most of the controls expose. Effective docking can help decrease those problems. If you're not starting with a clean surface, though, pay close attention to the order in which controls are added to the container's (ex: Form) Controls collectoin. They must be added in reverse order. For instance, if you have the "explorer layout" like so:
+-+---+
| | |
| | |
+-+---+ , you'll want a TreeView, Panel (to further dock additional controls), or some other control set to <cod>DockStyle.Left, then a splitter, then another control with DockStyle.Fill. The order in which these are added are in reverse of how I mentioned them:
Controls.AddRange(new Control[]
{
panel2,
splitter1,
panel1
});When you add these controls to the designer for the first time (i.e., on a "clean surface"), add them in the order that I first mentioned above. VS.NET automatically adds the most recently added control as the first control in the array above.
Just play around with docking a little bit. Anchoring to opposing sides is also helpful but while docking and anchoring share some behavior in common, they are also used to solve distinct problems (they are most like each other when anchoring against opposing and adjacent sides, but docking can't move a control relative to adjacent sides).
-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----
|
|
|
|
|
DockStyle in IMO is the easy way out, if you want control, use anchors.
leppie::AllocCPArticle("Zee blog");
Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.
|
|
|
|
|
The problem with anchors is that theyonly anchor to the parent control/form, and when the control/form shrinks the controls overlap.
The problem with docking is that the change in size is only shown in the fill'd control, and there is only one of these.
What you want is to have the control container resize the child controls, for that you need to create an "AutoSizePanel", have that dock'd fill and then set your controls on the panel.
Here is the code for the "AutoSizePanel":
using System;
using System.Collections;
using System.ComponentModel;
using System.Drawing;
using System.Data;
using System.Windows.Forms;
namespace Workbench
{
/// <summary>
/// A panel that resizes controls automatically.
/// </summary>
public class AutoSizePanel : Panel
{
/// <summary>
/// Holds the control info.
/// </summary>
private Hashtable htInfo = new Hashtable();
/// <summary>
/// Flag to prevent recursive call.
/// </summary>
private bool bAllowResize = true;
/// <summary>
/// Required designer variable.
/// </summary>
private System.ComponentModel.Container components = null;
/// <summary>
/// Constructor.
/// </summary>
public AutoSizePanel()
{
InitializeComponent();
}
/// <summary>
/// Adds a control to the list of controls.
/// </summary>
/// <param name="e"></param>
protected override void OnControlAdded(ControlEventArgs e)
{
// Hold the resizing
bAllowResize = false;
// Create the original info
SizingInfo riData = new SizingInfo(e.Control);
// Add to table
htInfo.Add(e.Control, riData);
// BAck to normal
bAllowResize = true;
//
base.OnControlAdded (e);
}
/// <summary>
/// Removes a control from the list of controls.
/// </summary>
/// <param name="e"></param>
protected override void OnControlRemoved(ControlEventArgs e)
{
// Delete the info
htInfo.Remove(e.Control);
//
base.OnControlRemoved (e);
}
/// <summary>
/// Does the magic.
/// </summary>
/// <param name="e"></param>
protected override void OnResize(EventArgs e)
{
// Only once
if (bAllowResize)
{
// Set
bAllowResize = false;
// And apply to each control
foreach (Control ctl in this.Controls)
{
// Get the original info
SizingInfo riCtl = htInfo[ctl] as SizingInfo;
// Info available?
if (riCtl != null)
{
// Resize
riCtl.Resize(ctl);
}
}
// Reset
bAllowResize = true;
}
//
base.OnResize (e);
}
protected override void OnPaint(PaintEventArgs e)
{
// Hold the resizing
bAllowResize = false;
// Collect info
foreach (Control ctl in this.Controls)
{
// Get the original info
SizingInfo riCtl = htInfo[ctl] as SizingInfo;
// Info available?
if (riCtl != null)
{
// Update
riCtl.Update(ctl);
}
}
// Back to normal
bAllowResize = true;
//
base.OnPaint (e);
}
/// <summary>
/// Clean up any resources being used.
/// </summary>
protected override void Dispose( bool disposing )
{
if( disposing )
{
if(components != null)
{
components.Dispose();
}
}
base.Dispose( disposing );
}
#region Component Designer generated code
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
//
// AutoSizePanel
//
this.Name = "AutoSizePanel";
this.Size = new System.Drawing.Size(232, 184);
}
#endregion
/// <summary>
/// This holds the original control information.
/// </summary>
private class SizingInfo
{
/// <summary>
/// Info to be kept.
/// </summary>
public int iTop;
public int iLeft;
public int iHeight;
public int iWidth;
public int iParentHeight;
public int iParentWidth;
/// <summary>
/// Constructor
/// </summary>
/// <param name="ctl"></param>
public SizingInfo(Control ctl)
{
// Save
this.Initialize(ctl);
}
/// <summary>
/// Updates the internal info
/// </summary>
/// <param name="ctl"></param>
public void Update(Control ctl)
{
// Compute the change.
double dRatioHeight = (double) ctl.Parent.Height / iParentHeight;
double dRatioWidth = (double) ctl.Parent.Width / iParentWidth;
// And where it would go.
int iWTop = (int) (iTop * dRatioHeight);
int iWHeight = (int) (iHeight * dRatioHeight);
int iWLeft = (int) (iLeft * dRatioWidth);
int iWWidth = (int) (iWidth * dRatioWidth);
// Changes?
if ((iWTop != ctl.Top) || (iWLeft != ctl.Left) || (iWHeight != ctl.Height) || (iWWidth != ctl.Width))
{
// Reset
this.Initialize(ctl);
}
}
/// <summary>
/// Does the magic
/// </summary>
/// <param name="ctl"></param>
public void Resize(Control ctl)
{
// Compute the change.
double dRatioHeight = (double) ctl.Parent.Height / iParentHeight;
double dRatioWidth = (double) ctl.Parent.Width / iParentWidth;
// And shake it
ctl.Top = (int) (iTop * dRatioHeight);
ctl.Height = (int) (iHeight * dRatioHeight);
ctl.Left = (int) (iLeft * dRatioWidth);
ctl.Width = (int) (iWidth * dRatioWidth);
}
/// <summary>
/// Saves the base info
/// </summary>
/// <param name="ctl"></param>
private void Initialize(Control ctl)
{
// Save
iTop = ctl.Top;
iLeft = ctl.Left;
iHeight = ctl.Height;
iWidth = ctl.Width;
iParentHeight = ctl.Parent.Height;
iParentWidth = ctl.Parent.Width;
}
}
}
}
This code is being made available to all freely.... Have fun, but do not copyright.
|
|
|
|
|
je_gonzalez wrote:
The problem with anchors is that theyonly anchor to the parent control/form, and when the control/form shrinks the controls overlap.
Hopefully at that stage the user realises that his an idiot, and the app wont run at 20 x 40 px. 
leppie::AllocCPArticle("Zee blog");
Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.
|
|
|
|
|
First, I am assuming that you have never dealt with marketing, as users are never idiots, and your app should run at 20 by 40. I solve it by making the controls really small, and then it becomes a hardware problem as the monitor is not able to display them properly.
Second, you should be PC and not assume that all users are male. This is assuming that you meant to type "the user realizes that he is an idiot", if not my apologies.
|
|
|
|
|
Please use C# to Print the following :
1
12
123
1234
12345
1235
124
1245
125
13
134
1345
135
14
145
15
2
23
234
2345
235
24
245
25
3
34
345
35
4
45
5
|
|
|
|
|
Console.WriteLine("1");
Console.WriteLine("12");
Console.WriteLine("123");
Console.WriteLine("1234");
Console.WriteLine("12345");
Console.WriteLine("1235");
Console.WriteLine("124");
Console.WriteLine("1245");
Console.WriteLine("125");
Console.WriteLine("13");
Console.WriteLine("134");
Console.WriteLine("1345");
Console.WriteLine("135");
Console.WriteLine("14");
Console.WriteLine("145");
Console.WriteLine("15");
Console.WriteLine("2");
Console.WriteLine("23");
Console.WriteLine("234");
Console.WriteLine("2345");
Console.WriteLine("235");
Console.WriteLine("24");
Console.WriteLine("245");
Console.WriteLine("25");
Console.WriteLine("3");
Console.WriteLine("34");
Console.WriteLine("345");
Console.WriteLine("35");
Console.WriteLine("4");
Console.WriteLine("45");
Console.WriteLine("5");
--Colin Mackay--
EuroCPian Spring 2004 Get Together[^]
|
|
|
|
|
|
I love your reply. It's so humorful hah...
|
|
|
|
|
using System;
using System.Text;
using System.Text.RegularExpressions;
using System.Drawing;
using System.Collections;
namespace CodeProject
{
class SillyStuff
{
[STAThread]
static void Main(string[] args)
{
ArrayList list = new ArrayList();
bool[] patt = new bool[] {false, false, false, false, false};
bool keeptruckin = true;
while (keeptruckin)
{
keeptruckin = false;
for (int loop1 = patt.GetLowerBound(0); loop1 <= patt.GetUpperBound(0); loop1++)
{
if (!patt[loop1])
{
patt[loop1] = true;
keeptruckin = true;
break;
}
else
{
patt[loop1] = false;
}
}
if (keeptruckin)
{
string buffer = string.Empty;
for (int loop2 = patt.GetLowerBound(0); loop2 <= patt.GetUpperBound(0); loop2++)
{
if (patt[loop2]) buffer += (loop2 + 1).ToString();
}
list.Add(buffer);
}
}
list.Sort();
for (int loop3 = 0; loop3 < list.Count; loop3++)
{
Console.WriteLine(list[loop3]);
}
Console.WriteLine("DONE");
}
}
}
|
|
|
|
|
You were subtle!
You got my 5!
Trying to make bits uncopyable is like trying to make water not wet.
-- Bruce Schneier
By the way, dog_spawn isn't a nickname - it is my name with an underscore instead of a space. -- dog_spawn
|
|
|
|
|
|
I want to add a text box into a template column during runtime. I can add a
boundcolumn but not with template column. I allow user to type in something
in the textbox in the datagrid. I wanna know if it's possible
public void AddNewColumn(DataGrid grid,string headerName)
{
TemplateColumn bc = new TemplateColumn();
............... something here
.................
grid.Columns.Add(bc);
}
Thanks
|
|
|
|
|
caheo wrote:
can add a
boundcolumn but not with template column.
Sure you can! Just do something like this:
<ItemTemplate>
<asp:TextBox id="tb1" runat="server"
Text="<%# DataBinder.Eval(Container.DataItem, "ColumnName") %>"/>
</asp:TextBox>
</ItemTemplate>See the documentation for TemplateColumn.ItemTemplate[^] for more information and a more thorough example.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----
|
|
|
|
|
How can i remove this for a encryption program it won't let me make it so it shows up NOT as a '?'? Any help?
|
|
|
|
|
or even better make it show up as a hex char i dont know how though any ideas?
- LiquidKnight
|
|
|
|
|
You shouldn't be trying to display encrypted blocks in a TextBox - it's always binary until encoded in base64 or something else (base64 is most common, though).
See the ToBase64Transform and FromBase64Transform classes in the .NET base class library. The class documentation also includes a couple of good samples for how to use these two classes. You should then have no problems displaying cipher text.
Just as examples, consider PGP (http://www.pgp.com[^]): in order to send plain-text cipher text as email (it's primary use is for communications) it must be encoded. This is currently done using base64. Or when you sign-up for an SSL certificate your request must be sent using a base64 encoded public key.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----
|
|
|
|
|
I've built a fairly complex stored procedure that has a couple of selects in it that are only functional while I'm only interested in reading the resultset from the last select.
Now when I fill my dataset, apart from retrieving useless data from the database, I have to acess my data doing something like ds.Tables[2].Rows
I have thought of two possible solutions even though I don't know how to implement any of them.
1. Have the stored procedure return only the last recordset. If this is possible I'm missing some T-SQL command. Anybody on this?
2. Give a name to the table that I'm interested in reading so that I could access it disregarding it's index like ds.Tables["MyRecordset"].Rows
This is much more elegant than accessing with numeric index bacause if I change the stored procedure I don't have to change my code.
Anyway how does one give a name to a table from a stored procedure?
Thanks
Edd
|
|
|
|
|
If you are using a DataAdapter to fill you dataset you can always create a strong typed dataset which allows you to access the data as:
myDs.MyTableName[row].MyField;
or
dsMyStrongType.MyStrongTypeRow dr = myDs.MyTableName[row];
dr.MyField = something
Makes life a lot easier and less apt to have typos on field names (plus you get Intellesense). Just build your DataAdapter in the editor and the right click on it to generate a dataset. If your stored procedure returns multiple results it will build a table by name for each. You can also select the table mapping property to call the tables anything you like.
Really cool stuff.
Rocky <><
www.HintsAndTips.com
|
|
|
|
|
Add an output parameter to the stored procedure and send the Table using it.
Send me the query.
Free your mind...
|
|
|
|
|
When using DataSets, try designing a strongly-typed DataSet by using the DataSet designer in VS.NET (there are other ways and tools, too, but I present the way in VS.NET). Right-click on your project or subfolder and select Add New Item. Find DataSet, give it a name, and click OK.
You'll see a component designer screen. Right-click to add elements (tables) and each element has rows and their types (the columns). You can even add relationships and primary keys. Just play around with it a little.
You can even use the Server Explorer if you have a database connection to drag-n-drop tables or stored procedures which returns tables to generate these automatically.
When you fill the strongly-typed DataSet, your DbDataAdapter derivative (like SqlDataAdapter) has to be configured to map the tables. This is done through DbDataAdapter.TableMappings and can easily be configured by using the data adapter designer in VS.NET as well.
Finally, you don't even need to use strongly-typed if you use the TableMappings property mentioned above. When selecting multiple result sets, the sequence of table names is "Table", "Table1", "Table2", etc. If you map these to other names, you can use DataSet.Tables["nameOfTable"].
I recommend using strongly-typed DataSets, though. You can easily refer to columns by name and don't have to worry about casting since those named rows return the appropriate Type.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.21
GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++
-----END GEEK CODE BLOCK-----
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
