| Age | Commit message (Collapse) | Author |
|---|
|
It's a common UI pattern to use an ellipsis to indicate an ongoing
action, rather than just specifying the word by itself.
|
|
|
|
game_list: Remove a reference of a reference
|
|
settings: Add support for setting the RTC manually
|
|
applets: Implement HLE web browser applet (LibAppletOff)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Stored as signed seconds since epoch.
|
|
gl_shader_cache: Use dirty flags for shaders
|
|
|
|
service/vi: Unstub IApplicationDisplayService's SetLayerScalingMode
|
|
qt: Move profile manager to own UI tab
|
|
gl_rasterizer_cache: Use GL_STREAM_COPY for PBOs
|
|
Since the data is doing the path CPU -> GPU -> GPU copy is the most
approximate hint. Using GL_STREAM_DRAW generated a performance warning
on Nvidia's stack. Changing this hint removed the warning.
|
|
service/vi: Correct reported dimensions from IApplicationDisplayService's GetDisplayResolution()
|
|
These values are not equivalent, based off RE. The internal value is put
into a lookup table with the following values:
[3, 0, 1, 2, 4]
So the values absolutely do not map 1:1 like the comment was indicating.
|
|
Avoids entangling the IPC buffer appending with the actual operation of
converting the scaling values over. This also inserts the proper error
handling for invalid scaling values.
|
|
This appears to only check if the scaling mode can actually be
handled, rather than actually setting the scaling mode for the layer.
This implements the same error handling performed on the passed in
values.
|
|
Return no application area when games try to open an application area
|
|
Proper no message handling for AM::PopMessage
|
|
GetDisplayResolution()
Within the actual service, it makes no distinguishing between docked and
undocked modes. This will always return the constants values reporting
1280x720 as the dimensions.
|
|
|
|
Pulse is considered a hack and nothing should be using it. We should completely remove it
|
|
service/vi: Minor updates and corrections to the DisplayInfo struct
|
|
This will prompt CreateApplicationArea
|
|
When we have no messages, we should be returning an error code.
|
|
testing to confirm)
Upon investigating the issue with #1878, I found that games are the ones who handle the vsync event resetting and not us.
|
|
service/vi: Implement OpenDefaultDisplay in terms of OpenDisplay
|
|
service/vi: Implement SetDisplayEnabled()
|
|
qt: Add setting to prompt for user on game boot
|
|
qt: Use ProfileSelectionDialog when selecting user for save data
|
|
This IPC command is simply a stub inside the actual service itself, and
just returns a successful error code regardless of input. This is likely
only retained in the service interface to not break older code that relied
upon it succeeding in some way.
|
|
service/vi: Log more information where applicable
|
|
In many cases, we didn't bother to log out any of the popped data
members. This logs them out to the console within the logging call to
provide more contextual information.
|
|
Internally within the vi services, this is essentially all that
OpenDefaultDisplay does, so it's trivial to just do the same, and
forward the default display string into the function.
|
|
gl_rasterizer_cache: Texture view if shader samples array but OGL is not
|
|
Based off RE, it appears that almost all display types seem to use
1920x1080 except for a few (null display, edid display).
|
|
It appears that the two members indicate whether a display has a bounded
number of layers (and if set, the second member indicates the total
number of layers).
|
|
Port citra-emu/citra#4187: "Qt/Configure: Use sidebar to divide tabs into smaller groups"
|
|
yuzu: Fix truncation warnings within UI code
|
|
The QPixmap API expects an unsigned int.
|
|
|
|
Gets rid of a few unnecessary header dependencies in some source files.
|
|
arm_interface: Minor cleanup
|
|
This is a bounds check to ensure that the thread priority is within the
valid range of 0-64. If it exceeds 64, that doesn't necessarily mean
that an actual priority of 64 was expected (it actually means whoever
called the function screwed up their math).
Instead clarify the message to indicate the allowed range of thread
priorities.
|
|
Now that we handle the kernel capability descriptors we can correct
CreateThread to properly check against the core and priority masks
like the actual kernel does.
|
