Age | Commit message (Collapse) | Author |
|
|
|
Before, the warning dialog would be opened after the NewProjectDialog,
leading to focus-fighting by the two windows. This fixes that and makes
the action more consistent with the standard serenity way of handling
unsaved changes by asking before the NewProjectDialog is brought up.
The way this is achieved avoids having to rewrite open_project as well.
|
|
This commit fixes a crash that would occur due to an unnamed file being
automatically saved via EditorWrapper::save(). Now, we throw up a
FilePicker::get_save_filepath.
|
|
There were a lot of unrelated formatting changes in the patch, which is
now shrunk by roughly 60%.
|
|
Our DynamicLoader would choke on a couple of missing symbols. I'm not
certain how this could have worked before, but there we go. :^)
|
|
All commits have been combined into one platform support patch.
|
|
SDL2 applications are prone to reinitializing the SDL components when,
for example, changing the display resolution. This would lead to
crashes since we were doing things in the wrong order.
* We now decouple `GLContext` from `SDL_Window` a bit more, allowing
the window to be destroyed before the GLContext.
* Do not quit the `GUI::Application`, let our event loop handle exiting
These changes allow changing the display resolution in the Quake3 port.
|
|
Specializing point_position_to_preferred_cell for the
RectangleSelectTool as it selects a new cells with a rounding
behavior instead of a flooring behavior
|
|
When handling mouse events, different tools may want to interact
with a different pixel in the image for the same input position.
|
|
This is done to allow querying the current active tool inside the
event_with_pan_and_scale_applied and event_adjusted_for_layer
functions without risking a null pointer dereference
|
|
This method is used to point a position at the preferred pixel of
the image. Certain tools may want to specify a different preferred
pixel for the same input position.
|
|
|
|
When the location currently displayed in FileManager is removed, find
the nearest existing parent path and open it in the window.
Without the fix, the FileManager window remained in the deleted
directory.
Changing the path in 'DirectoryView' object will automatically update
other components in the FileManager (breadcrumb bar, directory tree
view).
|
|
This commit fixes FileSystemModel behaviour when the root path of the
model has been deleted.
In this case, the model index resolved for the root path is invalid and
passing it to 'begin_delete_rows' would trigger assertion failure.
Instead of deleting all children rows one by one, we simply invalidate
the whole model.
|
|
ðū - U+1F33E SHEAF OF RICE
ðŋ - U+1F33F HERB
ðļ - U+1F378 COCKTAIL GLASS
ð - U+1F3E0 HOUSE
ðĄ - U+1F3E1 HOUSE WITH GARDEN
ðĨ - U+1F94F FLYING DISC
ð - U+1F3D1 FIELD HOCKEY
ð - U+1F3D2 ICE HOCKEY
ð - U+1F3D3 PING PONG
ðđïļ - U+1F579 JOYSTICK
ð§ - U+1F3A7 HEADPHONE
|
|
ðĒ - U+1F4A2 ANGER SYMBOL
ðŽ - U+1F4AC SPEECH BALLOON
ðĶī - U+1F9B4 BONE
ðĨĨ - U+1F965 COCONUT
ðĨ - U+1F95E PANCAKES
ð - U+1F359 RICE BALL
ð - U+1F382 BIRTHDAY CAKE
ðĨĪ - U+1F964 CUP WITH STRAW
ð - U+1F3DB CLASSICAL BUILDING
âĻïļ - U+2668 U+FE0F HOT SPRINGS
ð - U+1F383 JACK-O-LANTERN
ð - U+1F004 MAHJONG RED DRAGON
ð - U+1F50B BATTERY
ð - U+1F50C ELECTRIC PLUG
ðĨïļ - U+1F5A5 U+FE0F DESKTOP COMPUTER
ðĨ - U+1F5A5 DESKTOP COMPUTER
ðą - U+1F5B1 COMPUTER MOUSE
ð - U+1F4CB CLIPBOARD
ð - U+1F512 LOCKED
ð - U+1F513 UNLOCKED
ð - U+1F51E NO ONE UNDER EIGHTEEN
âïļ - U+2640 FEMALE SIGN
âïļ - U+2642 MALE SIGN
ð° - U+1F7F0 HEAVY EQUALS SIGN
âūïļ - U+267E INFINITY
|
|
This is a normative change in the Intl.DurationFormat spec. See:
https://github.com/tc39/proposal-intl-duration-format/commit/1304e4b
|
|
This is a normative change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/3a46ee3
|
|
These are editorial changes in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/71b291b
https://github.com/tc39/proposal-intl-duration-format/commit/d0cc6fa
https://github.com/tc39/proposal-intl-duration-format/commit/d4b35bb
|
|
This is an editorial change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/f947239
|
|
This is an editorial change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/527ea58
|
|
This is an editorial change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/cea3b68
|
|
This is an editoral change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/62ee645
|
|
These are normative changes in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/e2e18d1
https://github.com/tc39/proposal-intl-duration-format/commit/f1e8ed3
https://github.com/tc39/proposal-intl-duration-format/commit/2ed31b8
https://github.com/tc39/proposal-intl-duration-format/commit/2d51d64
https://github.com/tc39/proposal-intl-duration-format/commit/64cc5db
https://github.com/tc39/proposal-intl-duration-format/commit/a1d7876
https://github.com/tc39/proposal-intl-duration-format/commit/47a3a69
https://github.com/tc39/proposal-intl-duration-format/commit/3e9358e
https://github.com/tc39/proposal-intl-duration-format/commit/f4ecb46
https://github.com/tc39/proposal-intl-duration-format/commit/b454c8c
|
|
This is a normative change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/b289494
|
|
This is a normative change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/ac7e184
|
|
This is a normative change in the Intl.DurationFormat proposal. See:
https://github.com/tc39/proposal-intl-duration-format/commit/63a9202
|
|
And adjust some GML properties. Since a808cfa, splitters grow
opportunistically. Setting them to fixed sizes now quite literally
fixes them in place. Fixes immovable splitters missed in the
aforementioned commit.
|
|
test262's INTERPRETING.md specifies the exact steps for this function,
so let's shuffle some things around and add "spec" comments.
Most importantly this now returns the result of the evaluated script,
which at least one test relies on:
https://github.com/tc39/test262/blob/main/test/built-ins/Proxy/revocable/tco-fn-realm.js
|
|
This now matches the newly added string_to_number().
|
|
This was never caught since the original implementation AFAICT, and
isn't being covered by test262 either:
https://github.com/tc39/test262/issues/1354
|
|
This regressed in f4b3bb5.
|
|
Implements support for parsing binary and octal literals, and fixes
instances where a hex literal is parsed in ways the spec doesn't
allow.
|
|
ðĪ° - U+1F930 Pregnant Woman
ð§ - U+1F9CC Troll
ðĶ - U+1F998 Kangaroo
ðĶ - U+1F98B Butterfly
ð - U+1F6CC Person in Bed
ð― - U+1F33D Ear of Corn
ðĶ - U+1F526 Flashlight
ðŊ - U+1F3AF Bullseye
ðī - U+1F374 Fork and Knife
ðĩ - U+1F375 Teacup Without Handle
ðŪ - U+1F3EE Red Paper Lantern
ðķ - U+1F376 Sake
ðŧââïļ - U+1F43B_U+200D_U+2744 Polar Bear
ðĨĒ - U+1F962 Chopsticks
ðĨ - U+1F952 Cucumber
âĒïļ - U+2122 Trade Mark
ð - U+1F38B Tanabata Tree
ðī - U+1F6F4 Kick Scooter
âžïļ - U+203C Double Exclamation Mark
âïļ - U+2049 Exclamation Question Mark
|
|
Before of this patch, we supported two methods to address a boot device:
1. Specifying root=/dev/hdXY, where X is a-z letter which corresponds to
a boot device, and Y as number from 1 to 16, to indicate the partition
number, which can be omitted to instruct the kernel to use a raw device
rather than a partition on a raw device.
2. Specifying root=PARTUUID: with a GUID string of a GUID partition. In
case of existing storage device with GPT partitions, this is most likely
the safest option to ensure booting from persistent storage.
While option 2 is more advanced and reliable, the first option has 2
caveats:
1. The string prefix "/dev/hd" doesn't mean anything beside a convention
on Linux installations, that was taken into use in Serenity. In Serenity
we don't mount DevTmpFS before we mount the boot device on /, so the
kernel doesn't really access /dev anyway, so this convention is only a
big misleading relic that can easily make the user to assume we access
/dev early on boot.
2. This convention although resemble the simple linux convention, is
quite limited in specifying a correct boot device across hardware setup
changes, so option 2 was recommended to ensure the system is always
bootable.
With these caveats in mind, this commit tries to fix the problem with
adding more addressing options as well as to remove the first option
being mentioned above of addressing.
To sum it up, there are 4 addressing options:
1. Hardware relative address - Each instance of StorageController is
assigned with a index number relative to the type of hardware it handles
which makes it possible to address storage devices with a prefix of the
commandset ("ata" for ATA, "nvme" for NVMe, "ramdisk" for Plain memory),
and then the number for the parent controller relative hardware index,
another number LUN target_id, and a third number for LUN disk_id.
2. LUN address - Similar to the previous option, but instead we rely on
the parent controller absolute index for the first number.
3. Block device major and minor numbers - by specifying the major and
minor numbers, the kernel can simply try to get the corresponding block
device and use it as the boot device.
4. GUID string, in the same fashion like before, so the user use the
"PARTUUID:" string prefix and add the GUID of the GPT partition.
For the new address modes 1 and 2, the user can choose to also specify a
partition out of the selected boot device. To do that, the user needs to
append the semicolon character and then add the string "partX" where X
is to be changed for the partition number. We start counting from 0, and
therefore the first partition number is 0 and not 1 in the kernel boot
argument.
|
|
Similar to the find_last_split_view() helper, but in this helper we
search for the first split view instead of the last one.
|
|
|
|
Previously, for a regex such as /[a-sy-z]/i, we would incorrectly think
the character "u" fell into the range "a-s" because neither of the
conditions "u > s && U > s" or "u < a && U < a" would be true, resulting
in the lookup falling back to assuming the character is in the range.
Instead, first explicitly check if the character falls into the range,
rather than checking if it falls outside the range. If the explicit
checks fail, then we know the character is outside the range.
|
|
|
|
Now that the GC allocator is able to invoke Cell subclass constructors
directly via friendship, we no longer need to keep them public. :^)
|
|
This will allow Heap to invoke non-public constructors when allocating
new cells.
|
|
|
|
This is similar to what we already had with JS_OBJECT (and also
JS_ENVIRONMENT) but sits at the top of the Cell inheritance hierarchy.
|
|
The Quake 3 port makes use of this extension to determine a more
efficient multitexturing strategy. Since LibSoftGPU supports it, let's
report the extension in LibGL. :^)
|
|
On Arch Linux, the build was picking up the system libsamplerate, which
is undesirable. Unlikely that it is needed on Serenity, so disabling it
is a good workaround.
|
|
|
|
|
|
|
|
|
|
Defer creation of the global object to Realm::set_global_object(), and
use the newly added set_default_global_bindings() AO as intended.
|