Ping -- is anyone seeing this report? @dwmw2 wonder if you might be able to flag it with a relevant contributor? Looks like a pretty minor GUI issue...?
Hi Michael,
I think that I, personally, would rather not have this overlaid text appearing in front of the document I am reading. I would be interested to see ideas that provide some visual clue to return back to a previous page, but without overlaying on the all-important document itself. After all, one can imagine documents for which reading-and-clicking results in many layers of click-through, and this 'back to link' could be there nearly all the time. Perhaps one could use back/forward buttons in the title bar of Evince, which only appear (or or be visually activated/highlighted) when there are links in the stack.
Gnome Settings has such a back-button (although it's weird how it displays on my system, because of where I set the 'close window' button to be):
I am also not sure how often a click-through changes the zoom level, it's not something I remember noticing in documents that I have read. But if that's something that happens, then presumably if the click-through changes the zoom, then clicking back should restore it. I personally don't think it needs a special overlay 'restore zoom'. But maybe you could provide an example of a document that has this zoom-changing behaviour so we can take a look.
Cheers JP
I note that, in Evince 3.36.10 (on Ubuntu 20.04), there is a keyboard-based feature for moving to the 'previous page visited'. I would have assumed that this works after each clicked link. However, when I type Alt-P
as suggested, I get taken back to the first page of my document, not to the place I was before clicking the link. This appears to be incorrectly implemented. The request above would be a graphical way of doing the same, but at least it would be nice if the keyboard way works!
(PS my usual bugbear with GNOME3: features that don't appear in the menu, people don't know about... Old fashioned File Edit ... Help menus are much better for feature discovery!)
I have got the following versions of network-manager-openconnect installed, see below. This is on Ubuntu 20.04. Every time I connect to my VPN, a dialog pops up asking for the username of the connection. It remembers the password, but not the username. It looks like a bug... but perhaps I misconfigured it somehow?
john@ovo:~$ dpkg -l "*openconnect*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================================-============-============-===========================================================================
ii libopenconnect5:amd64 8.05-1 amd64 open client for Cisco AnyConnect, Pulse, GlobalProtect VPN - shared library
ii network-manager-openconnect 1.2.6-1 amd64 network management framework (OpenConnect plugin core)
ii network-manager-openconnect-gnome 1.2.6-1 amd64 network management framework (OpenConnect plugin GNOME GUI)
ii openconnect 8.05-1 amd64 open client for Cisco AnyConnect, Pulse, GlobalProtect VPN
When running ipython_view.py standalone, the output redirection appears not to be working correctly. Specifically, I get red text appearing on my output, as shown below.
Additionally,
io.IOStream
being deprecated.Having said all this, I think this is an awesome little piece of code and hope it keeps being maintained an improved. We've been using it to embed IPython in our equation-solving tool, ASCEND, https://ascend4.org/.
I found that when editing for example this file, https://github.com/modelica/ModelicaStandardLibrary/blob/master/Modelica/Blocks/Types.mo, the documentation strings are not properly formatting in Gedit - escaped quotes are being treated as the end of the string. I believe that this change corrects the issue.
No understanding escaped double quote character results in bad formatting when editing Modelica files. For example try the file https://github.com/modelica/ModelicaStandardLibrary/blob/master/Modelica/Blocks/Types.mo. This change hopefully fixes the issue, and makes reference to the Modelica syntax documentation (see embedded comment).
John Pye (37b0bd97) at 18 Sep 09:33
Fixed escaping in quoted strings.
I found that when editing for example this file, https://github.com/modelica/ModelicaStandardLibrary/blob/master/Modelica/Blocks/Types.mo, the documentation strings are not properly formatting in Gedit - escaped quotes are being treated as the end of the string. I believe that this change corrects the issue.
John Pye (015236e9) at 18 Sep 09:21
Correct string escaping in modelica.lang
I also found these, don't know if it's helpful or not: https://github.com/Ordissimo/scangearmp2 and https://launchpad.net/~thierry-f/+archive/ubuntu/fork-michael-gruz.
Hi @aklapper, I downloaded a current version of simple-scan from gitlab (40.1) and repeated the test. It is still doing the same thing. Although I suspect the root cause is the SANE backend, it still seems to me to be a bug that simple-scan just keeps scanning the flatbed over and over, rather than disallowing this option for cases where a sheet feeder is unavailable.
My debug output includes
[+0.11s] DEBUG: scanner.vala:1596: SANE version 1.0.29
I also downloaded and compiled SANE backends version 1.0.32 and installed using ./configure --prefix=$HOME/.local && make -j8 && make install
(and I needed to install autoconf-archive
to get that running) but I don't know how to get simple-scan to use this newer version of SANE. Can you point me at any instructions on how to do that?
With simple-scan 3.36.3 on Ubuntu 20.04, and having installed the .deb cnijfilter2-6.00-1 (amd64), I attempted to 'scan all pages from sheet feeder'. When I do this, the scanner starts scanning from the flatbed, and keeps on re-scanning over and over again. It doesn't stop.
I don't know if this is an issue with underlying libraries or with simple-scan itself. If there are any further tests I can run, please let me know.
Here is some output from scanimage
, if it helps. It seems that, in contrast to this output, my output does not show a way of specifying the 'source' of the image. At the same time, the Canon open-source tool 'scangearmp2' (download here), does managed to pull from the feeder, and stops quickly. It just doesn't have the nice simple-scan GUI!
john@ovo:~/scangearmp2-source-4.00-1$ scanimage -d escl:https://10.1.1.205:443 -A
Output format is not set, using pnm as a default.
Capability : [image/jpeg]
Capability : [image/jpeg]
Capability : [image/jpeg]
Capability : [image/jpeg]
scanimage: rounded value of br-x from 0 to 0
scanimage: rounded value of br-y from 0 to 0
All options specific to device `escl:https://10.1.1.205:443':
Scan mode:
--mode Gray|Color [Gray]
Selects the scan mode (e.g., lineart, monochrome, or color).
--resolution 75|100|150|200|300|600|1200dpi [75]
Sets the resolution of the scanned image.
--preview[=(yes|no)] [no]
Request a preview-quality scan.
--preview-in-gray[=(yes|no)] [no]
Request that all previews are done in monochrome mode. On a
three-pass scanner this cuts down the number of passes to one and on a
one-pass scanner, it reduces the memory requirements and scan-time of
the preview.
Geometry:
-l 0.0846558..215.9mm [0]
Top-left x position of scan area.
-t 0.0846558..297.011mm [0]
Top-left y position of scan area.
-x 0.0846558..215.9mm [0]
Width of scan-area.
-y 0.0846558..297.011mm [0]
Height of scan-area.
With simple-scan 3.36.3 on Ubuntu 20.04, and having installed the .deb cnijfilter2-6.00-1 (amd64), I attempted to 'scan all pages from sheet feeder'. When I do this, the scanner starts scanning from the flatbed, and keeps on re-scanning over and over again. It doesn't stop.
I don't know if this is an issue with underlying libraries or with simple-scan itself. If there are any further tests I can run, please let me know.
I also see this issue with Gnome Font Viewer 3.28.0 and libfreetype 2.8.1 on Ubuntu 18.04, with the Public Sans font from https://fonts.google.com/specimen/Public+Sans#standard-styles.
Additionally, I note (this is a freetype bug, perhaps, more than Gnome), when I click to install 'PublicSans-VariableFont_wght.ttf' from that package, the font appears with inconsistent naming in both Gnome Font Viewer and in LibreOffice.
"Public Sans" but the first line of the window says "Public Sans Thin" and it does appear to show the 'Thin' variant, but gives no indication of the other weights available. Then, in LibreOffice, the font appears as "Public Sans Thin", even if I choose a different weight eg "Black" weight of "Public Sans Light". If I meanwhile attempt to choose "Public Sans", it will work, but "Black" is not shown as an available option.
Finally, if "fc-list | grep Public" then I get the following output, which also seems to suggest that the variable-weight font has been unpacked incorrectly, with the 'Thin' name included against all variables for some reason:
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Thin
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=ExtraLight Italic
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Black
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Thin Italic,Italic
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=ExtraBold
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Bold
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Thin,Regular
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Bold Italic
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Regular
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=SemiBold
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Medium
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Light
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=ExtraBold Italic
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Light Italic
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Medium Italic
/home/john/.local/share/fonts/PublicSans-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=ExtraLight
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Black Italic
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Thin Italic
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=SemiBold Italic
/home/john/.local/share/fonts/PublicSans-Italic-VariableFont_wght.ttf: Public Sans,Public Sans Thin:style=Italic
I also posted here, with freetype: https://gitlab.freedesktop.org/freetype/freetype/-/issues/1067
Simplescan is very nice. I especially like the 'reorder pages' feature (although I find its placement in the hamburger menu a little strange).
One little issue though: it seems that after scanning multiple pages (like 20 or so), it is not possible to scroll easily through the page view.
Perhaps mouse-wheel event binding could be added to allow scrolling (horizontally) through the collection of scanned pages? Something that also works with the trackpad, too, perhaps? The GNOME scroll bars are so hard to grab hold of these days, it really needs scroll wheel support for usability.
Although there have lots of great improvements, there has been a general deterioration in the keyboard accessibility of GNOME apps since the 'File, Edit, View' menus went away. It would be great if this issue could be addressed a bit systematically somehow... Putting everything behind the F10 key is a bit of a cop-out, I feel. Discoverability is important, too.