Advanced Forum Search Results
-
Hi Jesse,
The link you've posted redirects to my own direct messages. I think it is supposed to be like this: twitter.com/.../must-read-silverlight
Thank you for sharing anyway!
Timmy Kokke
-
I did not know that! Thanks. It works as intended now…
-
Both .zip files are available here: http://cid-3bfc746510bc922d.skydrive.live.com/browse.aspx/.Public
The .fx can be found in the silverlight version. The WPF version uses the exact same .ps file.
-
The performance is great. But there result is totally different. The shader in WPF shows a refraction effect, distortion as if looking thru water. In Silverlight it shows diagonal bars moving, as it the rounding goes wrong or something. I thought (was hoping actually) that Silverlight 3 was using the GPU.
-
Hi,
Does anyone know what's different in rendering shaders in WPF and Silverlight? I've writing a couple of shaders, and they look good in WPF but look awefull in silverlight. I assumed the rendering of the Shaders would be done by the GPU in both situations.
Does anyone else has experience with this difference?
-
In silverlight this isn't possible. But, in WPF you can render to a bitmap and save this to disk or return it as an byte array. I assume the xaml assets you're talking about aren't that complicated and silverlight specific and will work in a WPF app.
Last month I use this in a PHP project to generate images on the server using ...
-
I just realized i've been editing the wrong file for out-of-browser all along.... The AppManifest.XML file is used to generate the AppManifest.XAML file (which is located in the Bin/Debug folder). I had to edit the XML version instead of the XAML one... my mistake.
Anyway. I've been doing some testing, and I think the application ...
-
What happens if you let visual studio create a new appmanifest.xaml file? rename the appmanifest.xaml file to .bak or something and build it again. a new appmanifest file should be created. If you remove the comments to enable OOB and run it. Does it work than?
If not, than this problem is likely to be cause by anything else than the ...
-
I think this is caused by the Deployment.Parts section being empty. It should contain something like:
<Deployment.Parts>
<AssemblyPart x:Name="ProjectName" Source="ProjectName.dll" />
</Deployment.Parts>
-
If you look closely at this effect you'll see that it are only a few layers responding the movement of the mouse. Here's how it's done:
Add a MouseMove event handler to the LayoutRoot Grid. Next, add 3 grids the LayoutRoot and name these BackgroundLayer1, 2 and 3. In the example below I've added a few ellipses to the ...