Age | Commit message (Collapse) | Author |
|
The point of positioning the selected item is that it must remain at
the correct origin. Now it just needs a scrolling feature that
checks mouse hover position on overflow widgets.
|
|
Changing the fonts, zoom level, or window width will cause cached documents to be laid out again if they are restored from memory.
|
|
Platform convention.
|
|
IssueID #372
|
|
Kudos to Alyssa Liddell for a 100% translation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As soon as the first part of a response is available, update the page theme and banner.
|
|
The warning about terminal emulation can be dismissed on site-specific basis.
Banner items show a hover frame (like buttons) to indicate they can be clicked.
|
|
Warn the user about missing glyphs and potentially unsupported ANSI escapes.
TODO: Site-specific setting for dismissed warning; fonts preference about missing glyph warnings.
|
|
|
|
|
|
|
|
Banner will take over everything related to the page top banner.
DocumentWidget's content positioning is a bit messy, and now that the banner is no longer part of the GmDocument, it needed a bit of revising. It would still benefit from proper functions for mapping coordinates to/from the GmDocument coordinate space.
|
|
|
|
|
|
|
|
The token is saved just like the text editor content.
In a single panel layout, the Upload button should only be shown when a detail panel is visible.
The text editor panel shouldn't scroll because the input widget does its own scrolling.
|
|
|
|
Include a padding under the buttons to account for the toolbar.
|
|
|
|
|
|
|
|
|
|
Tab close button visibility, newly added preferences, "Manage Fonts" button, button icon color.
|
|
No need to use Garbage here to collect per-frame strings and arrays.
|
|
The hover widget needs updating if the currently visible tab changes. Normally the hover widget is only updated when the mouse has moved.
|
|
|
|
IssueID #354
|
|
|
|
An [x] button appears on tab buttons when hovering on them. Still needs a bit of layout tweaks and the first tab doesn't have a button yet.
|
|
The windowID was expected to be set, but wasn't for touch events.
IssueID #351
|
|
|
|
|
|
The invalid runs were sometimes discarded before they had a chance to be drawn.
|
|
|
|
IssueID #358
# Conflicts:
# res/lang/de.bin
# res/lang/en.bin
# res/lang/eo.bin
# res/lang/es.bin
# res/lang/es_MX.bin
# res/lang/fi.bin
# res/lang/fr.bin
# res/lang/gl.bin
# res/lang/ia.bin
# res/lang/ie.bin
# res/lang/isv.bin
# res/lang/pl.bin
# res/lang/ru.bin
# res/lang/sk.bin
# res/lang/sr.bin
# res/lang/tok.bin
# res/lang/zh_Hans.bin
# res/lang/zh_Hant.bin
|
|
When GlyphBuffers were freed, the array holding them wasn't.
|
|
FG color and font style escapes can be enabled separately. FG color remains enabled by default like before.
|
|
Don't try to show a document while a long download is progressing, especially if we don't have any way to present the document format.
|
|
When GlyphBuffers were freed, the array holding them wasn't.
|
|
|
|
Saving this as the last point of progress. This direction is too complicated: Media needs to be a lot more sophisticated to allow dynamic and interactive media at the level of FontPacks. (A bit like Player handles audio playback.)
This will be reverted. FontPack management will happen using an another method.
|
|
When the last safe break position was not in the current attributed run, the calculated wrap advance came out incorrect. This was possible when the first glyph in an attributed run didn't fit.
|