WPF UserControl Library - I'm at a loss [modified] - WPF Discussion Boards

23-Apr-09 0:28

If I was doing this, I'd normally update the model behind this, and let binding update the checkboxes rather than specifically update the checkboxes.

"WPF has many lovers. It's a veritable porn star!" - Josh Smith

As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.

Re: binding problem

User 171649223-Apr-09 1:25

User 1716492

23-Apr-09 1:25

Congrats Pete. Saw your article in yesterday's "UK MSDN Flash". Thumbs Up | :thumbsup:

modified 1-Aug-19 21:02pm.

Re: binding problem

Pete O'Hanlon23-Apr-09 1:42

23-Apr-09 1:42

Thanks for that. It was a real problem keeping an article I'm passionate about down to 500 words. There was a severe amount of pruning involved.

"WPF has many lovers. It's a veritable porn star!" - Josh Smith

As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.

Print Datatable

Prajeesh22-Apr-09 19:06

Prajeesh

22-Apr-09 19:06

Hi,

I have a datatable as

DataTable dt = new DataTable( "Table1" );
dt.Columns.Add( "c1" );
dt.Columns.Add( "c2" );
dt.Columns.Add( "c3" );
DataRow dr = dt.NewRow();
dr["c1"] = "100";
dr["c2"] = "100";
dr["c3"] = "100";
dt.Rows.Add( dr );
dt.AcceptChanges();
printListView.DataContext = dt;

I have also a listview for showing the table.
<ListView
HorizontalAlignment="Stretch"
HorizontalContentAlignment="Stretch"
SelectionMode="Single"
ItemsSource="{Binding}"
Name="printListView"
Margin="10">
<ListView.View>
<GridView>
<GridViewColumn Header="c1" DisplayMemberBinding="{Binding c1}"/>
<GridViewColumn Header="c2" DisplayMemberBinding="{Binding c2}"/>
<GridViewColumn Header="c3" DisplayMemberBinding="{Binding c3}"/>
</GridView>
</ListView.View>
</ListView>

How can I print this table?

Thanks
Prajeesh Prabhakar

Re: Print Datatable

Pete O'Hanlon23-Apr-09 22:17

23-Apr-09 22:17

What I would do is create a FixedDocument which contains a Table that uses the datasource that you are using here, rather than using a ListView. Then, you use a DocumentPaginator and use this with PrintDialog.PrintDocument.

"WPF has many lovers. It's a veritable porn star!" - Josh Smith

As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.

WPF UserControl Library - I'm at a loss [modified]

#realJSOP22-Apr-09 3:58

#realJSOP

22-Apr-09 3:58

How do you change the protection level of a control within a usercontrol when said usercontrol is in a WPF usercontrol library?

In my solution, I have a a WPF UserControl library project that contains several UserControl objects.

Ive got a WPF Application project that contains a window object that uses two user controls - one is a toolbar (in the library project), and the other is a general content control in the application project.

I'm trying to add a button handler for a toolbar button. Because the controls inside a user control are all marked as "internal", I can't add a button handler in the "code behind" (what a stupid f*ckin way to have to say "real goddamn code", but I gigress).

So how do I accomplish what I want if all the frakking controls are internal?

"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001

modified on Wednesday, April 22, 2009 10:20 AM

barker77022-Apr-09 6:06

barker770

22-Apr-09 6:06

You probably want your toolbar button to be bound to a command:

Open...

If it is a standard command, such as file open, use the commands provided by the ApplicationCommands class as shown above. If not, create and register your own new command (must be static).

In your app code, bind a method to that command. That method will get called when the command "is raised". It's just like registering for an event, with one level of decoupling.

This "decoupling" between the UI and the rest of the app is a key idea of WPF. In WPF, you should not be directly linking to event handlers of a specific button. By using a command, the UI can be changed from a button to some other control type, and the command is still the same. If you wiered up directly to the event handler, then if you change the button to another type, you would have to find all places that event was being handled, and then change the event handler signature.

I've only been using WPF for about 2 months, and I share your frustration. You must see the WPF light Wink | ;-)

resistance is futile...

Mitch

led mike23-Apr-09 10:00

led mike

23-Apr-09 10:00

barker770 wrote:
This "decoupling" between the UI and the rest of the app is a key idea of WPF

Are you sure? We've been doing that for years before WPF came along. I thought there was more to it than that.

barker770 wrote:
You must see the WPF light

You could have used a CP Holy Grail Smiley right about then eh? Wink | ;)

Pete O'Hanlon23-Apr-09 0:16

23-Apr-09 0:16

John - you can change the visibility of controls by specifying a FieldModifier, e.g. x:FieldModifier="public".

"WPF has many lovers. It's a veritable porn star!" - Josh Smith

As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.

#realJSOP23-Apr-09 2:45

#realJSOP

23-Apr-09 2:45

Yeah, I found that out, but somehow it didn't seem to be the "WPF way". The guy before you posted what I think might be the "WPF way". Have I mentioned how badly WPF sucks yet today?

Michael Bookatz23-Apr-09 4:34

Michael Bookatz

23-Apr-09 4:34

John Simmons / outlaw programmer wrote:
Have I mentioned how badly WPF sucks yet today

I don't think you have at least not enough. I think you're starting to get into a love\ hate relationship with it. Just ask it out on a date already!!!

#realJSOP23-Apr-09 4:56

#realJSOP

23-Apr-09 4:56

I actually do love hating it because in my own way, I'm justified in hating it.

led mike23-Apr-09 10:05

led mike

23-Apr-09 10:05

John Simmons / outlaw programmer wrote:
Have I mentioned how badly WPF sucks yet today?

I'm still standing on the sidelines watching. Sort of like the jury is still out, you know? I mean the historical perspective on WPF could end up being, "The best implementation of a bad idea ever". Of course there can be no doubt that my perspective will be proved wrong one day when computers just do what we want them to do without us having to tell them what to do. $Shucks | :-\$ Jig | [Dance]

0x3c023-Apr-09 10:21

0x3c0

23-Apr-09 10:21

led mike wrote:
my perspective will be proved wrong one day when computers just do what we want them to do without us having to tell them what to do

Never going to happen[^]

Clearing the screens

Hema Bairavan22-Apr-09 0:28

Hema Bairavan

22-Apr-09 0:28

Hi peoples,

I am working in WPF screen,
i need to clear all the controls(values) in the screen at one stretch,
if win forms we can give as (foreach control in this.controls)

but here how can we do??

Re: Clearing the screens

Jeeva Jose22-Apr-09 3:05

Jeeva Jose

22-Apr-09 3:05

Please use the following code in C#

this.Content = null;

Continue...

Re: Clearing the screens

Pete O'Hanlon22-Apr-09 3:39

22-Apr-09 3:39

This doesn't work with TextBoxes, TextBlocks or Labels.

"WPF has many lovers. It's a veritable porn star!" - Josh Smith

As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.