Forum Replies Created
-
AuthorPosts
-
TorParticipant
The right click behaviour can be customized, you can check your current configuration by clicking the small menu icon in the top bar, select “Configure Desktop” in the popup, click “Mouse Actions” in the Desktop Folder Settings window
and verify that “Right-Button” action is associated to “Standard Menu” in the combo box.TorParticipantHi. We can verify if the settings directory is somehow causing issues. Please right click the NoMachine dock icon and quit the application. Open the Terminal and execute the command
mv $HOME/.nx $HOME/nx_backup
, then try to start again NoMachine. Is the app starting now, or does it has the same behaviour?TorParticipantHi. Locally on your Mac, is the Control + Left click on the desktop opening the context menu, like the right mouse click normally does? Do you use settings or applications changing keys mapping?
What is the operation you’re trying to execute on the remote server with the emulated right click? We didn’t reproduce issues with it, but we’d like to run a test closer to your working conditions.TorParticipantHi. You can notice that fonts have increased to your DPI setting, but layouts and icons didn’t increase as well. There is no way right now to improve that unfortunately. We’re working on some changes for HiDPI displays, which will also introduce improvements to the general UI look.
TorParticipantHi. What’s the output of command
echo $WAYLAND_DISPLAY
executed in a terminal window on both servers?TorParticipantHi! The screenshot is showing workspaces, but I’m not sure to understand how you would like to use them.
Do you mean you’ve multiple monitors connected to the server, and you want to know how to select them individually?November 19, 2021 at 20:59 in reply to: How to treat multi-monitors on client as separate monitors in virtual sessions #36356TorParticipantIf you have more than one monitor connected to the client host, please write a few details like Operating System name and version, number of monitors, name of graphical adapter and drivers version. If your client runs on Linux, attach to the answer also the output of the command
xrandr -q
executed in a terminal window.November 19, 2021 at 19:48 in reply to: How can connect to a NoMachine server by means of a command line in Cent OS 8? #36355TorParticipantHi. You can execute the nxplayer command with the
--session
option, for example/usr/NX/bin/nxplayer --session ~/Documents/NoMachine/Connection\ to\ 192.168.2.1.nxs
.November 16, 2021 at 14:54 in reply to: How to treat multi-monitors on client as separate monitors in virtual sessions #36256TorParticipantHi! After selecting the “Resize remote display” option did you click the “Fullscreen on all monitors” button? Going fullscreen is required to mirror the client monitors geometries and layout on server side.
TorParticipantI cannot seem to use Ctrl on Windows to send Cmd in Mac.
Do you refer in particular to copy&paste operations? Are there other shortcuts you’re not comfortable with as Windows user connected to a Mac desktop?
Like Britgirl said we’re working on the feature, but any additional information you could give can be useful.October 28, 2021 at 19:04 in reply to: NoMachine switched language to an old system language after update #35999TorParticipantHi. The language you select in the installer changes only the EULA, it doesn’t affect the software language.
Open NoMachine client, click Settings, select Appearance and choose your language in the combo box on the right page. We’ll check the reason why the language automatically switches to a different language, but the configuration above should be enough to solve your problem.October 25, 2021 at 13:33 in reply to: Allow NoMachine window between screens with Shift+Win+arrow #35933TorParticipantHi. We’ve no problems to use the Windows + Shift + Arrows key combinations on NoMachine windows, to move them between monitors, minimize, etc. Those are functionalities offered by the window manager and we never had to support them explicitely.
Can you maybe give more context or any information useful to run a few more checks on our side?TorParticipant(perhaps this can be adjusted with the wmctrl but I am not familiar with its options)
Apologies, I did a bad assumption! You can replace the action “toggle” with “add”, so it will only enable fullscreen and it won’t remove it when its already set.
TorParticipantHi. Client stores the last window state and restores it when starting, and currently there is no way to avoid that.
You could do what you need with a tool like ‘wmctrl’ by creating a script to start the client, or by editing the script /usr/NX/bin/nxplayer in a way similar to this:exec "$NX_SYSTEM/bin/nxplayer.bin" "$@" & sleep 1 wmctrl -x -r nxplayer.bin -b toggle,fullscreen wmctrl -x -R nxplayer.bin
We’ll evaluate adding a command line option to always start in fullscreen mode by ignoring the last saved window state.
TorParticipantYou could configure the client CFG to skip that message, by setting the following key to ‘false’:
<option key="Show local desktop connection information" value="false" />
Normally this CFG is located in $HOME/.nx/config, but you can start the client with an option to load the CFG from different paths:
/usr/NX/bin/nxplayer --config /path/player.cfg
The file ‘nxplayer’ is a script, you could edit it to add the ‘–config’ option.
Meanwhile we’ll check how to improve the conditions triggering that message to avoid to show it in similar environments.
-
AuthorPosts