3644b442fa
Unless, of course, it has the B_BITMAP_CLEAR_TO_WHITE flag as well. From my testing, not clearing the BBitmap matches BeOS's behaviour more closely (if not exactly) compared to clearing the BBitmap. My test program created the BBitmap and BView, drew a diagonal red line across it, and saved the result to a file. The results: * BeOS - transparent background; red line with no anti-aliasing * Haiku, current behaviour - white background; red line * Haiku, new behaviour - transparent background; red line with black pixels as artifacts of the anti-aliasing process. The anti-aliasing artifacts, as PulkoMandy pointed out, are simply a result of not using the B_OP_ALPHA and an appropriate blending mode, and would happen on BeOS as well if the line had some transparency, such as through anti-aliasing. Change-Id: I09ac054eb0ce79e697b78ea48d1db4a15041e600 Reviewed-on: https://review.haiku-os.org/c/haiku/+/7899 Haiku-Format: Haiku-format Bot <no-reply+haikuformatbot@haiku-os.org> Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: waddlesplash <waddlesplash@gmail.com> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk>
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.