* -l now lists the contents of string B+trees.
* -c now counts the keys in a B+tree.
* Use BPLUSTREE_MAX_KEY_LENGTH to determine the maximum allowed
key length (was hardcoded to 255 before).
* The maximum key length of the B+tree, and the one BFS uses are now
separated. This allows to stay BeOS compatible to only put a maximum
of 255 bytes into the index, but also to handle the already existing
larger keys (we did allow 256 bytes) without issue.
* TreeIterator::Traverse() now always cuts off string keys at the
maximum buffer length, and only reports a B_BUFFER_OVERFLOW for the
fixed length types.
* This fixes the important part of #13254.
The goal of sanitize_display_mode is to create a mode that the hardware
can use. The code was doing that, but if any change was required to the
initial mode, it threw the result away.
Now accept the sanitized mode, and log it for debugging purposes.
This should fix#12927
* IOBuffer::FreeVirtualVecCookie() did not put the last physical page
back. This was only an issue in case GetNextVirtualVec() wasn't
iterated through the end, for example in case of an error.
* Fixed the condition when to put back a physical page; the current
solution will also work with the generic page mapper implementation.
* This fixes the low hanging fruits of Ingo's comment in #5777.
* device_removed() no longer uses get_device_interface() to avoid
the double locking.
* Introduced net_device_interface::busy member to avoid locking in
device_removed() for too long.
* This should fix#7252.
* Both functions need to wait when encountering a busy vnode, in order
not to create a race condition in combination with get_vnode().
* This should fix both #5262, and #9839.
* I did not implement Ingo's suggestion to burden the file systems with
solving the problem for the following reasons:
- I think the file system interface should be as simple as possible.
- I can't think of a possible locking issue at least for BFS.
- The solution on the file system side would look pretty similar to
what the VFS already does or has to do (minus controlling the locking
directly), so it would cause quite a functional duplication.
As pointed by Marcus, FindString returns a pointer to the internal data
of the BMessage, so the message must stay in scope as long as we use the
pointer.
Thanks for reviewing!
ffmpeg, especially older versions, is not very good at detecting file
types and relies on us giving it a file extension for a better guess.
Use our MIME sniffing to have a first try at detecting the file we are
about to play, and pass this information to ffmpeg.
Fixes#13150.
*Bug fix- list item colors use Appearance settings
*Problem Solver window buttons right aligned, window now app modal
*The main window's stripe and icon now use the same scaling as BAlert
*A pop-up menu displays an option to view more details (replaces the
tooltips)
*New prompt at application start to choose between doing an Update or
a Full Sync. Also lays the ground work for implimenting silent
check-only feature.
Needed a quick new release:
* Fix disappearing favorites.
* Add context menu with quick access to favorites and QuickLaunch's
"About" to Deskbar replicant.
* Updated localization and documentation.
* Tiny tweaks to the QuickLaunch icon.
fActiveSoundFont wasn't initialized when there's no midi_settings file.
Don't allocate it on the heap, the object get implicitely initialized to
an emtpy string.
Tiny style fix.
Thanks to AnEvilYak for his consultation.
Fixes#13402.
* The previous xhci endian fixes performed some double
conversions.
* Tighten down conversions to only where the driver interacts
with raw trb3 data in the ring buffer
* No impact to x86*
