aboutsummaryrefslogtreecommitdiffstats
path: root/vncviewer
Commit message (Collapse)AuthorAgeFilesLines
...
* Add client-side support for the MSLogonII security type.Dinglan Peng2022-12-271-0/+2
|
* Add client-side support for the DH security type.Dinglan Peng2022-12-271-0/+6
|
* Merge pull request #1525 from pdlan/add-ra2-javaBrian Hinz2022-12-221-0/+1
|\ | | | | Add support for RSA-AES security types (Java version)
| * Fix missing RA2ne enabling in storeOptions()pdlan2022-09-031-0/+1
| |
* | Merge branch 'newoptions' of https://github.com/CendioOssman/tigervncPierre Ossman2022-12-2216-372/+789
|\ \
| * | Respect system UI fontPierre Ossman2022-12-221-3/+34
| | | | | | | | | | | | | | | | | | Use the font specified by the system for UI elements. For Windows and macOS this is straight forward, but Linux is more complex as there is no single source for this information.
| * | Fix up padding for radio/check buttonsPierre Ossman2022-12-221-3/+3
| | | | | | | | | | | | | | | | | | | | | Try to follow the actual padding that FLTK adds to these widgets. The extra one pixel on each is because of a bug in FLTK's focus drawing code, where the box is always one pixel too small in both dimensions.
| * | Reduce indent to same as a normal marginPierre Ossman2022-12-221-1/+1
| | | | | | | | | | | | | | | This is how GNOME does things, so let's do the same so things look similar.
| * | Wider margin around window edgesPierre Ossman2022-12-222-3/+3
| | | | | | | | | | | | To conform with how e.g. GNOME sets its margins.
| * | Dynamically size Fl_Group:sPierre Ossman2022-12-221-32/+28
| | | | | | | | | | | | This makes the code much cleaner, and easier to update.
| * | Make UserDialog use standard layout constants.Pierre Ossman2022-12-221-21/+30
| | | | | | | | | | | | Makes it easier to adjust the UI from a central place.
| * | Make ServerDialog use standard layout constantsPierre Ossman2022-12-221-35/+35
| | | | | | | | | | | | Makes it easier to adjust the UI from a central place.
| * | Modern look for options sectionsPierre Ossman2022-12-222-43/+52
| | | | | | | | | | | | | | | Outlines are no longer commonly used. Instead visually separated headlines are the norm.
| * | Change to modern layout in options dialogPierre Ossman2022-12-225-11/+273
| | | | | | | | | | | | | | | | | | | | | | | | | | | Classical tabs are very dated. They are also a practical problem as you get very limited in the numbers of tabs we can have, and how long the text can be on them. Switch to one popular modern model with a list on the left instead where pages can be selected.
| * | Use standard accessors for Fl_Monitor_ArrangementPierre Ossman2022-09-073-11/+17
| | | | | | | | | | | | | | | The accessor functions are called value() for all standard FLTK widgets, so let's keep that theme here as well.
| * | Rename MonitorArrangement to Fl_Monitor_ArrangementPierre Ossman2022-09-075-31/+31
| | | | | | | | | | | | | | | Follow upstream FLTK naming to more clearly indicate that this is a general widget and not TigerVNC specific.
| * | Split general FLTK appearance to separate filePierre Ossman2022-09-074-23/+90
| | | | | | | | | | | | | | | These are general things and not specific to TigerVNC, so let's move it to the fltk specific directory for clarity.
| * | Split out FLTK utility functionsPierre Ossman2022-09-076-83/+114
| | | | | | | | | | | | | | | These have nothing to do with layout, so let's split them to their own file.
| * | Move general FLTK stuff to own directoryPierre Ossman2022-09-079-19/+25
| |/ | | | | | | | | | | | | Let's separate TigerVNC specific things from stuff that could be part of upstream FLTK. These are files that we would like to collaborate with other FLTK users, so they are more liberally licensed and avoid using TigerVNC specific things.
* | Rebuild .desktop and metainfo when neededPierre Ossman2022-12-191-0/+4
| | | | | | | | | | If the translations change then these files need to be regenerated as they include data from those.
* | Don't translate "RSA-AES"Pierre Ossman2022-12-151-1/+1
| | | | | | | | | | It's just the name of the system, so there is nothing in that string to translate.
* | Move window to front on full screenPierre Ossman2022-12-151-0/+5
| | | | | | | | | | This should be happening implicitly, but isn't always for some reason on macOS 13.
* | Handle macOS keyboard stealingPierre Ossman2022-12-134-4/+40
|/ | | | | | | | | | The system steals keyboard events for certain system keyboard shortcuts, e.g. Cmd+Tab. Unfortunately this isn't considered a focus loss, so we don't realise we've lost a few keyboard events and can end up in a confused state. Fortunately it is possible to detect when this happens and reset the keyboard state, just like we do when focus is lost.
* Add support for RSA-AES security typespdlan2022-09-014-11/+81
|
* Re-enable lock key sync in viewerPierre Ossman2022-08-311-1/+1
| | | | This was accidentally disabled in 81e114f.
* Fix encoding group for H.264 choicePierre Ossman2022-08-241-1/+4
| | | | It might not be compiled in, so the height needs to be dynamic.
* Fix "grave" and "ISO" keys on macOSPierre Ossman2022-08-232-2/+14
| | | | | We lacked an entry for one of these, and the magical swap that macOS does for unknown reasons.
* Add missing FLTK include statementsAlbrecht Schlosser2022-07-075-1/+6
| | | | Add also missing <stdlib.h> where required.
* Cork the proper output stream in the clientPierre Ossman2022-06-281-2/+2
| | | | | | The socket might not be the stream actually used, e.g. when we are using TLS. Make sure we cork the proper stream to get all the benefits of corking.
* Remove unnecessary flushPierre Ossman2022-06-281-1/+0
| | | | Uncorking implicitly flushes, so we don't need this.
* Fix up ffmpeg header and library handlingPierre Ossman2022-06-071-1/+1
| | | | | FFMPEG is needed by the RFB library, so all the details about it should only be applied there and not for other components.
* Avoid temporary cmake variablesPierre Ossman2022-06-071-16/+13
| | | | | Modern cmake has better support for adding source files and libraries incrementally, so let's use that to clean things up.
* Automatically generate Windows icon filePierre Ossman2022-05-111-1/+1
|
* Add more Unix icon sizesPierre Ossman2022-05-112-2/+2
| | | | | Some desktop environment, like KDE, need more rastered sizes and cannot make use of the SVG.
* Remove dead codePierre Ossman2022-05-111-6/+0
| | | | This code is never used on Windows, so remove it.
* Safer allocation of icon arrayPierre Ossman2022-05-111-1/+1
| | | | | Avoid the risk of the list of sizes and the list of icons getting out of sync and causing memory corruption.
* Fix bad indentation in CConn::socketEvent()Pierre Ossman2022-04-061-5/+5
|
* Ignore socket whilst processing dataPierre Ossman2022-04-061-2/+3
| | | | | | | | | | FLTK has a lot of synchronous stuff (like dialogs), which mean that the main loop might be run recursively in some cases. If there is data available on our socket then CConn::socketEvent() will be called constantly in a busy loop. Avoid this by removing socket notifications whilst we are processing data.
* Added AppStream meta info file for the vncviewerJoachim Falk2022-03-082-0/+73
|
* Added screenshots for AppStream meta info file for vncviewerJoachim Falk2022-01-283-0/+0
|
* Remove 32-/64-bit distinctionsPierre Ossman2022-01-212-10/+4
| | | | | The migration from 32-bit to 64-bit has long passed. Let's get rid of all distinctions as native applications it the norm now.
* Merge branch 'h264dec' of https://github.com/xornet-sl/tigervncPierre Ossman2022-01-213-3/+27
|\
| * H264 DecoderVladimir Sukhonosov2022-01-213-3/+27
| | | | | | | | Linux implementation using ffmpeg
* | Log objects should be localPierre Ossman2022-01-211-1/+1
|/ | | | Otherwise things might be logged under the wrong label.
* Always log screen layout if validation failsWilliam Sjöblom2022-01-191-3/+5
| | | | | Unconditionally log the erroneous screen layout if it fails to validate to simplify debugging.
* Fix session resize after mirroring on Linux vncviewerWilliam Sjöblom2022-01-191-2/+6
| | | | | | | | | | | | | | | If monitor mirroring was enabled while in a session with vncviewer running on Linux, the session would not be properly resized on the server. This was a consequence of only looking at the size and coordinates of each screen when matching against existing screens after the screen layout was changed, when in fact we have two (or more) monitors with the same coordinates and size (but differing ids). This led to the same monitor being added twice to the layout which would later fail layout validation, resulting in no resize request being sent to the server. When matching, we now also check if the existing screen is not already present in the layout before considering it a match.
* Improve full-screen workaround on connectPierre Ossman2022-01-121-5/+11
| | | | | | | | | | | | | | If we've explicitly requested a position (using -geometry) then we were still triggering legacy full-screen request logic. This is very counter intuitive as having a position that doesn't align with a monitor should disqualify us for that. It turns out that at least marco (and probably everything metacity-derived) ends up ignoring the requested position and we go back to triggering the legacy logic again. Work around this by assuming that the window manager will adjust our initial position and don't consider that in the workaround logic.
* Update MonitorArrangement widget after changeSamuel Mannehed2022-01-102-1/+41
| | | | | | | | | | | | | | | | | If the options dialog was open when a screen configuration happened the widget could get out of sync from the settings. A scenario when this happened was: 1) 3 monitors, fullscreen selected on the two right-most screens 2) disconnect the left-most screen (the one not selected) In this case, using GNOME, vncviewer would appear in fullscreen on the right of the two remaining monitors, but the widget would show both monitors selected. The reason was that the MonitorArragement index doesn't work the same way as FLTK's screen index. It's debatable how vncviewer should behave here, but the GUI should at least match the actual setting.
* Update copyright year to 2022Pierre Ossman2022-01-052-2/+2
|
* Don't add . to error message stringPierre Ossman2022-01-041-1/+1
| | | | | The norm is to have error strings without punctiation, so avoid adding one as it just confuses the translators.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-23 05:55:11 +0000