Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WritableBitmap is not updating after updating the BackBuffer #64605

Closed
alxkalinin opened this issue Feb 1, 2022 · 3 comments
Closed

WritableBitmap is not updating after updating the BackBuffer #64605

alxkalinin opened this issue Feb 1, 2022 · 3 comments
Labels
untriaged New issue has not been triaged by the area owner

Comments

@alxkalinin
Copy link

alxkalinin commented Feb 1, 2022

Description

The WritableBitmap can be used as the source of an Image. We can update the WritableBitmap BackBuffer dynamically to update the Image.

In my environment, the updating of the BackBuffer is not lead to updating the Image at all.

Reproduction Steps

Example 1

Compile and run WritableBitmap example from the .NET documentation.

Expected behavior: application draw pixels when the mouse moving on

Actual behavior: pixels are not drawn

Example 2

ScottPlot LiveDemo is not working on my environment. ScottPlot is based on WritableBitmap. See ScottPlot/ScottPlot#1600 (comment)

Expected behavior

Image should be updated after updating of the WritableBitmap

Actual behavior

Image is not updating

Regression?

No response

Known Workarounds

No response

Configuration

C:\Projects>dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.101
 Commit:    ef49f6213a

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19043
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.101\

Host (useful for support):
  Version: 6.0.1
  Commit:  3a25a7f1cc

.NET SDKs installed:
  6.0.101 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Device name	ASUS VivoBook
Processor	11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz   2.80 GHz
Installed RAM	16.0 GB (15.7 GB usable)
Device ID	5CF4A36A-2AED-420E-8E8C-EC21B342EA89
Product ID	00325-82192-41866-AAOEM
System type	64-bit operating system, x64-based processor
Edition	Windows 10 Home
Version	21H1
Installed on	‎2021-‎10-‎12
OS build	19043.1466
Experience	Windows Feature Experience Pack 120.2212.3920.0

Other information

No response

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 1, 2022
@alxkalinin
Copy link
Author

Related to the dotnet/wpf#3817

@alxkalinin
Copy link
Author

Fixed by updating Intel Graphics driver up to the version "30.0.101.1121".

@ghost ghost locked as resolved and limited conversation to collaborators Mar 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant