mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-10 23:44:24 +00:00
415aed4bea
When syncing from CPU->GPU storage, we currently copy the entire image contents. The contents of the CPU backup completely replace the old GPU image. Therefore, if any pixels need to retain their existing values, we need to read those pixels before overwriting them. This in turn implies that, when a BitmapData refers to a subsection of the image, we should always flush GPU->CPU storage first, so that the subsequent CPU->GPU sync doesn't clobber pixels outside of the BitmapData region with outdated values. It's clear that copying the entire image back and forth could be suboptimal when writing to image subsections, but to optimise this process we'd have to keep track of dirty image regions or similar, which may in turn pessimise more common cases. |
||
|---|---|---|
| .. | ||
| juce_analytics | ||
| juce_animation | ||
| juce_audio_basics | ||
| juce_audio_devices | ||
| juce_audio_formats | ||
| juce_audio_plugin_client | ||
| juce_audio_processors | ||
| juce_audio_utils | ||
| juce_box2d | ||
| juce_core | ||
| juce_cryptography | ||
| juce_data_structures | ||
| juce_dsp | ||
| juce_events | ||
| juce_graphics | ||
| juce_gui_basics | ||
| juce_gui_extra | ||
| juce_javascript | ||
| juce_midi_ci | ||
| juce_opengl | ||
| juce_osc | ||
| juce_product_unlocking | ||
| juce_video | ||
| CMakeLists.txt | ||