forked from FirestormViewer/phoenix-firestorm
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge master #2
Merged
Merged
merge master #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sed in the cpp translation unit
…a Swallowtail) and Polish translations
AiraYumi
pushed a commit
that referenced
this pull request
Apr 10, 2024
Set DONE if decode thread is down instead of waiting for an update. Decodes can't be canceled, so fix potential situation where we get two responses
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
List of removed preferences (usused per statistics): BottomPanelNew BrowserHomePage BlockSomeAvatarAppearanceVisualParams ButtonHPad ButtonHeight ButtonHeightSmall CacheNumberOfRegionsForObjects ChatBarStealsFocus ChatLoadGroupTimeout ChatPersistTime ChatShowTimestamps ContextConeInAlpha ContextConeOutAlpha ContextConeFadeTime ConversationHistoryPageSize ContactsTornOff CurlMaximumNumberOfHandles CurlUseMultipleThreads CustomServer DebugShowPrivateMem
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
Scaling was added to thumbnail images as a measure of memory preservation and said scaling doesn't work well when larger images are needed so had to remake profile images to no longer use thumbnails.
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
…fallback fonts. With the emojis support, a new font was added, which not only provides emojis but also fancy colorful replacements for UTF-8 characters that used to be supported by our fallback (monochrome) fonts: this causes discrepancies and unwanted/undesired changes in scripted objects menus (e.g. an empty circle or square may render as a black, full one, a heart may render red instead of white), not to mention the larger font size used by the emoji characters... This patch restores the aspect of such menus/dialogs/UI elements with UTF-8 characters that *are* supported by the usual fallback fonts (fonts which may also vary from one viewer to another, and from one OS to another), so that everything keeps working/rendering as it always did so far, while not impairing the use of new colorful emojis. This second proposal ensures that: - "genuine" emojis (in the 0x1f000-0x1ffff range), will *always* be rendered using the new emojis font (this solves, for example, the monochrome "yellow faces" issue seen with some characters in my first proposal). - Special UTF-8 characters (in the 0x2000-0x32FF range) which have been used by scripters so far, will render as they used to, using the monochrome fallback fonts (this repairs scripted dialogs menus). - Remaining special characters, that do not have a corresponding glyph in the monochrome font, but do have one in the emojis font, will use the latter font to render. It also got the nice side-effect of removing the dependency on the ICU4C library. Note however that the recent commit: secondlife/viewer@326055b will need to be reverted to allow this patch to actually fix scripted dialogs. Also, some cleanup might be needed in skins/default/xui/*/emoji_characters.xml to remove from it the special UTF-8 characters that will no longer be rendered with fanciful colors, but instead with the monochrome font glyphs.
AiraYumi
pushed a commit
that referenced
this pull request
May 18, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Jun 11, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Aug 27, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Aug 27, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Sep 20, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Sep 20, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Dec 19, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Dec 19, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Dec 19, 2024
AiraYumi
pushed a commit
that referenced
this pull request
Dec 19, 2024
Apparently made a blunder in previous commit since I missed mFetchState being reset each run
AiraYumi
pushed a commit
that referenced
this pull request
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.