|
Hi Gerhard,
I was having the same problem with vs2008 and the "Choose Items" command in the toolbox. Any chance you have Power Commands 2008 installed? I had it installed because it offered functionality to collapse all projects among other things. Well apparently there is some sort of comflict between vs 2008 and power commands 2008.
For more info visit: http://www.imaginativeuniversal.com/blog/VisualStudio2008SP1ToolboxCrash.aspx
Hope this helps,
proganon
|
|
|
|
|
Hi proganon,
no, there is a hot fix available, please read the older conversation items, and after applying this fix, the toolbox works fine.
With best regards
Gerhard
|
|
|
|
|
Ah, I missed that reply when I was reading through them...must've been a different problem or a different reason for the problem.
Thanks
|
|
|
|
|
Hi!
I need a small 3D feature for a WPF window and I don't know where to start.
I need a series of Pictures in a row like a carousel, but in a kind of theatre view. On Channel 9 is a Flickr viewer, but that is way tooo complex and uses mouse interaction (not what I need) and several rows (I just need ONE row) with a maximum number of 9 images.
The more "lightweight" the solution is, the better.
Any ideas?
Greetings,
Stephan Eberle
hawke@deltacity.org
|
|
|
|
|
Stephen - you may want to take a look at the options that Pavan has put together in Fluidkit[^]. This is probably what you want.
"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.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
Thank you for pointing out fluid! Looks promising.
Actually I was looking for a XAML snippet like handling two / three images in a Viewport3D view. Maybe any other documents/HowTos?
Best regards and thank's again!
Stevie
|
|
|
|
|
|
You could always use a method like this:
private void ChangeRowHeight(Grid grid, int row, int height)
{
grid.RowDefinitions[row].Height = new GridLength(height);
} So, to hide the 2nd row, you'd use
ChangeRowHeight(Details, 1, 0);
"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.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
I've got a 3D Control which based On Direct3D. And I found something interesting. In my window, I have a Grid as a root element which holds two children, the first one is my 3D contorl and another one is a rectangle.
<grid>
<mycontrol:3dcontrol xmlns:mycontrol="#unknown" />
<rectangle width="50">
Height="50"
Fill="Red"/>
</rectangle></grid>
I hope, as well as it seems to be,the Rectangle is on top of my 3DControl. But on the opposite, 3DControl is on the top of my rectangle.
Then I tried to set the Panel.ZIndex neither it work. Since many ways I've tried it still doesn't work, I started to judge the way of wpf d3d control mechainsm.
In some articles I learned Direct3D has two modes windowed and exclusive. Windowed needs back buffer bu Exclusive calls graphic driver directly. Is the Exclusive mode make my 3DControl always on the top? Oh by the way, mycontrol is inherited from WindowsFormHost class, is it caused the promblem either? Anyway so confused!!!!
modified on Tuesday, March 31, 2009 1:20 AM
|
|
|
|
|
I'm using MVVM in which WPF controls are data bound to propertied in a "ViewModel". This all works fine. One of our main controls is an XY chart and it can only be update via code because it requires looping and other logic. i.e it's not adaptable to data binding.
Since I cannot bind the chart to data, I was forced to add a method to the XAML code behind that knows how to update the chart. To further muddy the MVVM design pattern, I had to pass the View down to the ViewModel, so that the ViewModel could explicitly call the UpdateChart method that is in the View code behind.
Instead of binding between the ViewModel and UI control, I would like to bind between the ViewModel and a method in the code behind. Then the method in the code behind could go thru its complex logic to update the chart control.
Thanks for any suggestions. I appreciate the benfits of DataBinding and MVVM, but I can't make it work with my WinForms control that is embedded in a WindowsFormsHost control.
Mitch
|
|
|
|
|
barker770 wrote: pass the View down to the ViewModel
why would you do that ? You could bind in the view to change notification and update whenever there is a change?
|
|
|
|
|
ABitSmart wrote: why would you do that ? You could bind in the view to change notification and update whenever there is a change?
The view is bound to the view model, and I have implemented INotifyChange. This works for binding to WPF controls, but not for binding to my chart control that is in the WinFormsHost.
So the question remains, can I bind a method in my View to the ViewModel without explicitly passing the view object down to the viewModel object.
Mitch
|
|
|
|
|
barker770 wrote: Since I cannot bind the chart to data, I was forced to add a method to the XAML code behind that knows how to update the chart. To further muddy the MVVM design pattern, I had to pass the View down to the ViewModel, so that the ViewModel could explicitly call the UpdateChart method that is in the View code behind.
Why is this method not part of the ViewModel? If it's updating data, then it has no place in the view - the view should only be a visual representation.
"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.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
> Why is this method not part of the ViewModel? If it's updating data,
> then it has no place in the view - the view should only be a visual
> representation.
Agreed. And the procedural code in the View.xaml.cs code is really just to help transfer the data into the winforms control.
Yes, I would prefer to bind a chart property directly to a method in the ViewModel, but I need this procedural code to be somewhere. And it makes sense to make it part of the View. Just as somewhere in the standard WPF binding code there is some procedural code that does the actual display of the data.
It would be perfect if I could bind a method in the View.xaml.cs to my ViewModel In effect, encapsulating the logic needed to bind to the chart control inside the View (albeit the code behind for the View.
Mitch
|
|
|
|
|
If you just need to use the host because you have a none WPF chart, why not take a look at this[^]?
"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.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
A native chart is of course the best solution. However, we have a lot of expertise with this third party chart control (ChartFx) that it would be too costly in terms of time to abandon it now. We have several WinForms products and we have layered on many custom interactive chart features. We're starting a new product and want to use WPF for all but the chart.
ChartFx is developing a WPF native chart, but it may not have the same feature set nor does it's release schedule match ours.
Anyway, I did find the "PropertyMap" property of the WinFormsHost, but it only maps to properties of the winForms host class. Is there some way to add a new property? For example, I would map a new property named "DataSeries" to a method in the xaml.cs code. Then I would bind the "DataSeries" property to my ViewModel. Any tips on doing this?
Thanks,
Mitch
|
|
|
|
|
I think I answered my own question. Since the ViewModel implemented INotifyChangedProperty I just added an event handler in the view's code behind to listen for each event from the viewModel. When it's the even I want, I update the winforms chart.
This pseudo binding still relies on both the View and ViewModel to agree on a property name. But that's the nature of binding anyway.
Mitch
|
|
|
|
|
Congratulations. It's just a shame you've had to use the Interop Helpers; they are such a bind. Pun unintended.
"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.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
That was actually what I meant. I should have put in more details.
|
|
|
|
|
Hello!
I have such task - to create control that union two controls (DataGrid from WPFToolkit and standard Toolbar). On a large scale, it doesn't matter what particular controls it unions, I need to find out the common practices that can be used to build what I need. At first glance, I need something like user control, i.e composition of controls, that I can implement as a whole and reuse then. But, my task requires me to have possibility to tune my composite control in XAML. So, if I compose Toolbar and DataGrid, I want properties and events of both them would be exposed. So I could set in XAML both, for example, columns of datagrid and bars of toolbar:
(I put spaces in tag names intentionally, because loacal parser didn't type them for some reason)
< MyDataGridToolBarControl ><br />
< DataGrid ><br />
< DataGrid.Columns ><br />
< DataGridTextColumn Header="firstColumn" ><br />
< /DataGridTextColumn ><br />
< DataGridTextColumn Header="secondColumn" /><br />
< /DataGrid.Columns ><br />
< /DataGrid ><br />
< ToolBar Background="{x:Null}" > <br />
<button tooltip="New"><br />
<image source="New.png" /><br />
</button><br />
<button tooltip="Save"><br />
<image source="Save.png" /><br />
</button><br />
<button tooltip="Delete"><br />
<image source="Delete.png" /><br />
</button> <br />
< /ToolBar ><br />
< /MyDataGridToolBarControl >
The only decison that suits me less or mor for now is to make custom control inherited from Datarid (as DataGrid is more significant in this pair) and redefine Template including both datagrid and toolbar. This gives me all power of datagrid but, if I want get Toolbar part, I need to do it through code, seeking it in viual and logical trees i.e. getting access o it programmatcally, which is not pretty decision.
Please help a newbie to solve this task ) Thanks in advance...
|
|
|
|
|
You're obviously very new to this. Any property you add to your control, can be set from XAML.
Christian Graus
Driven to the arms of OSX by Vista.
"I am new to programming world. I have been learning c# for about past four weeks. I am quite acquainted with the fundamentals of c#. Now I have to work on a project which converts given flat files to XML using the XML serialization method" - SK64 ( but the forums have stuff like this posted every day )
|
|
|
|
|
Thats it, I'd like not to transmit every property and event of each component control to the level of composite control. I'd like (if it is posible) to inherit all of them! But multiple inheritance in c# is not allowed, so I can't go this way! So, because of it I am here and your answer is inappropriate. If you are lazy to answer, it would be better not answer at all. Thanks
|
|
|
|
|
Hi.
I'm working VS2008 SP1 and SilverLight 2.
My SL's Application has worked until 2 hours ago very well ,but Browsers just couldn't show it anymore.
BTW I change my project name manually
What's wrong with it ?
How can I fix it ?
Would appreciate for any guides.
|
|
|
|
|
If you changed the name of something, make sure the name is changed anywhere
in the code that's effected.
For example, if the name of the xap is now different, you may need to change
the reference to the xap in your hosting web page.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
I've done it, but it didn't work.
I forced to make a new Project.
Thanks anyway.
|
|
|
|