DWC on SBC question

[Carlo]

@chas2706
Open chromium enter the Pi ip 192.xxx.xx.xx
save as a favorite add to tool bar
Also hitting F11 exits full screen mode or touch screen hold finger on screen for couple seconds and Exit full screen with appear

[chas2706]

@Carlo said in DWC on SBC question:

@chas2706
Open chromium enter the Pi ip 192.xxx.xx.xx
save as a favorite add to tool bar
Also hitting F11 exits full screen mode or touch screen hold finger on screen for couple seconds and Exit full screen with appear

Great. Thanks for that.

[A Former User]

@Carlo said in DWC on SBC question:

Open chromium enter the Pi ip 192.xxx.xx.xx

as dwc is running on the same host using http://localhost/ would make more sense and not be dependant on user networks which may differ from 192.168/16

if exiting full screen works then find launch-dwc and remove --start-fullscreen. if that doesn't work toggle overscan settings in raspi-config?

[chas2706]

Thanks both of you.
All sorted now.

[A Former User]

would you mind sharing, others may find the thread useful later?

[chas2706]

Just making you aware that when I edited autostart in /etc/xdg/lxsession and put a hash in front of @launch-dwc, when I rebooted I found that DWC still autostarted.
In my duetpi image there is another autostart found in /home/pi/.config/lxsession/LXDE/autostart.
It has exactly the same content as the other one in etc/xdg/lxsession but this MUST be the one the pi is looking at. Hashed out in here and DWC does not autostart.

Also I found a quicker solution to my problem.
In chrome I set the home page as duet3.local/ then in /home/pi/.config/lxsession/LXDE/autostart I hashed out @launch_dwc and added @chromium-browser.
Now on startup I have chrome autostarting in windowed mode and connected to DWC.

[chas2706]

Here's a copy of the new autostart file:

@lxpanel --profile LXDE
@pcmanfm --desktop --profile LXDE
@xscreensaver -no-splash
@/home/pi/./atx_on.sh
#@launch-dwc
@chromium-browser

Once again, thanks everyone for your help.

[A Former User]

@chas2706 said in DWC on SBC question:

there is another autostart found in /home/pi/.config/lxsession/LXDE/autostart

huh, interesting, and redundant. wasn't clear from the DuetPi repo, but admittedly not familiar with pi-gen at all.

if fullscreen was the issue I'd lean towards editing launch-dwc and commenting out --start-fullscreen from there, then it works even if you add another user, change windowmanager or whatnot.

sudo sed -i 's/ --start-fullscreen/ #--start-fullscreen/' /usr/bin/launch-dwc should take care of it with a one-liner

[chas2706]

@bearer said in DWC on SBC question:

@chas2706 said in DWC on SBC question:

there is another autostart found in /home/pi/.config/lxsession/LXDE/autostart

huh, interesting, and redundant. wasn't clear from the DuetPi repo, but admittedly not familiar with pi-gen at all.
if fullscreen was the issue I'd lean towards editing launch-dwc and commenting out --start-fullscreen from there, then it works even if you add another user, change windowmanager or whatnot.
sudo sed -i 's/ --start-fullscreen/ #--start-fullscreen/' /usr/bin/launch-dwc should take care of it with a one-liner

Not so, because @launch-dwc does not have the extra --start-fullscreen parameters in it!

[A Former User]

it should
https://github.com/Duet3D/DuetPi/blob/master/stage-dsf-gui/00-autologin/files/launch-dwc#L3

(and mine did)

[chas2706]

Sorry, I was looking in the wrong place!
Going to try that now.

[chas2706]

You are a star.

Commenting out --start-fullscreen works and has the extra benefit of no page tabs or search bar so you basically get full screen but with the window control buttons.
Cheers.

[A Former User]

That might be the --app parameter that does that. Interesting learned something new today!

Anyways, glad it worked out!