* This parses the reported CPU name, and tries to translate it to a normal
and concise identifier.
* For example, it will translate "AMD FX(tm)-8320 Eight-core Processor" into
"FX™ 8320" or "Dual Core AMD Opteron(tm) Processor 275 HE" into
"Opteron™ 275 HE".
* This means we can remove AMD strings for those models for which this
function produces useful results.
* This can be done from the command line using the new "-open" option.
* When the application is invoked via Tracker, ie. by double clicking
on an image, then it's being used implicitly.
* For LVDS output, the sync parameters aren't really used which is why the mode
set from the BIOS might not be valid if the PLL hardware would actually be
used.
* Therefore, we sanitize this mode to make sure it's within allowed parameters
so that intel_set_mode() will accept it.
* This should fix at least #8132, and #8796.
* Sorry for looking into this so late! I obviously messed up testing this
before, as my EeePC 900 was actually affected by this, too.
* Does not seem to work yet, though. The intel disk system should support it
now, but apparently the partition's delegate is not yet fully initialized
for whatever reason.
* The normal mouse mode now only uses the window that had focus last if that
window is one that does not support to be the front window (such as the
desktop).
* This should keep the logic of r41264 without the drawbacks (see #7280 for
more information).
* Added _WindowCanHaveFocus() method.
* This should fix#7630.
* It uses size_for_string() to display all sizes which also fixes
using MiB for one, and MB for the other size string.
* It is no longer limited to 1M granularity by itself, but can have
arbitrary granularity as long as the number of possible values
remain smaller than 2^31.
* This means it can also handle values beyond 4TB now.
* The sizes that are set programmatically retain their full resolution.
* CreateParametersPanel still uses 1M granularity for now, though,
as we would otherwise need to be able to parse a size string with
a unit.
* Changed order of calling Init() vs. _CreateViewControls(). This
fixes bug #9422.
* The panel now hides (instead of disabling) the name or type control
if those aren't supported, anyway.
* The user of an editor needed knowledge about the editor in order to make
use of it.
* Furthermore, the BPartitionParameterEditor exposed type specific
functionality that it shouldn't know anything about, either.
* We may now define a number of known parameters per editor type; right now
there is only "type" as it's needed by DriveSetup.
* Adapted all disk systems, and DriveSetup to the new API.
* Renamed CreateParamsPanel, and InitializeParamsPanel to *ParametersPanel
in DriveSetup.
* They now share a common base class AbstractParametersPanel.
* The default width will no longer make the parameters and partition type
columns visible.
* Fixed default size of those two columns -- I did not notice that the column
state was being restored before, and thought it would just be another oddity
of BColumnListView :-)
* Since MainWindow maintains its size pretty much itself, the constructor no
longer gets a BRect.
* The window will now also be resized vertically to make space for all the
partitions (only affects first launch without settings file).
* Also made the window a bit higher by default.
* Instead of guessing whether or not to show the InitParamsPanel, the panel
will now no longer show itself if the disk system does not have an editor,
and silently succeed.
* This also fixed a potential crash if the editor could not be created for
some reason.
* Minor cleanup.
* The AHCI driver was actually ignoring sector size information, and always
set the size to 512.
* Now both, the AHCI driver, and the ATA bus manager, use the same method of
retrieving the sector count, and size.
* The header and table is now correctly written; the backup is still
missing, though.
* The Header class is now responsible for both, the primary, and the
backup header.
* Changed the Header constructors: the block is no longer needed. Also,
under GCC 4 the initialization code accidentally used the read
Header constructor.
* Fixed incorrectly copied GUID - the static_guid cannot be copied
into a guid_t directly.
* Fixed copy&paste bug that would overwrite the offset for the child
partition to be created.
* With all of this in place I successfully created a BFS partition
with a GUID partition table. However, I have not yet tested if other
systems can still read this. Also, creating two partitions doesn't
seem to work yet, either (luckily I only need a single one ;-)).
* Tried to use EFI::Header class, but there doesn't seem to be an easy
way to actually hit the disk -- which we'll have to do to find out
how large the GPT table is.
* Initialization of GPT disks is now working which is why I added the disk
system add-on to the image. However, there is a caveat, as the backup
header and table aren't written yet.
* Partitions can be deleted.
* Creating partitions does not work yet, but I don't know yet why; in
theory it could already work.
* Moved some functionality into their own files so that they can easily
be reused by other code.
* Added crc32() function from FreeBSD. Implemented CRC handling and
validation.
* Implemented missing write functionality.
* Apparently, the order the fields are set matters, so the drive name
and the size now appear in the list as they should have before.
* Leave the size field empty if the size is 0.
* The hashtable stored complete Inode objects (albeit without the actual block).
* Now we only store the block_run which should reduce the memory footprint
considerably; before "recover" could easily run out of memory. In any case,
a 64 bit version would still make sense to have :-)
* Saved an extra hash table traversal by counting the node types directly.
* This isn't that well tested yet, though.
* Original patch by Morgul as part of #4235. This does not close the ticket,
however.
* Updated the patch to not show empty '()' in case the partition type
returned was NULL.
I made the following changes to the original patch:
* Add const to the cursor setting functions.
* Removed the legacy cursor copying code.
* Minor coding style cleanup.
* This makes the keymap behave as in every other operating system.
* I don't really understand the original purpose of this change. Please
enlighten me (see #4464).
* Before, you had to have both, the text view layout item, and the label
layout item or else nothing would ever be visible.
* Now you can only create the text view item, and it will still work.
* Also, no matter the order you added the layout items, they would always
put the label on the left, and the control to the right.
* You can place the label and text view layout items anywhere now, although
you should keep in mind that the view spans over their frame unions; IOW
they should always adjacent to each other, but not necessarily horizontally
and left to right.
* No longer uses a fixed label spacing, but utilizes
BControlLook::DefaultLabelSpacing() instead.
* However, the spacing is always added to the right of the label, no matter
how you place it in the layout. Maybe one wants to add a SetLabelTextViewGap()
like method.
Axel Dörfler