When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen, ...
Louis Epstein <le@lekno.ws> writes:
When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen, ...
man 1 xinit says:
"Both the client program name and the server program name must begin
with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines."
-WBE
When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen, ...
man 1 xinit says:
"Both the client program name and the server program name must begin
with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines."
Is this a recent change to functionality?
I know "xinit openttd" worked before.
Louis Epstein <le@lekno.ws> posted:
When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen, ...
to which I replied:
man 1 xinit says:
"Both the client program name and the server program name must begin
with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines."
Louis Epstein <le@lekno.ws> replied:
Is this a recent change to functionality?
An xinit man page from 1990 that has copyright 1988 says the same thing,
so not what I'd call recently.
I know "xinit openttd" worked before.
Don't know. "xinit `which openttd`", which isn't much longer, should
work, I would think. If you define openttd as an environment variable,
you could even do "xinit $openttd". :)
The other thing I don't understand is why you need to do that at all.
X11 programs are entirely capable of having their window be full-screen
size even after a standard xinit/startx startup, so I would think you wouldn't need to do a special startup to get full-screen, unless that's
an openttd issue.
-WBE
X-window managers I've used have top/bottom bars that windows can't cover
and full-screen OpenTTD uses that space for key menu/status stuff.
Louis Epstein <le@lekno.ws> posted:
When I want to play OpenTTD full-screen,I have launched
"xinit openttd" and had this bring up the game full-screen, ...
to which I replied:
man 1 xinit says:
"Both the client program name and the server program name must begin
with a slash (/) or a period (.). Otherwise, they are treated as an
arguments to be appended to their respective startup lines."
Louis Epstein <le@lekno.ws> replied:
Is this a recent change to functionality?
An xinit man page from 1990 that has copyright 1988 says the same thing,
so not what I'd call recently.
I know "xinit openttd" worked before.
Don't know. "xinit `which openttd`", which isn't much longer, should
work, I would think. If you define openttd as an environment variable,
you could even do "xinit $openttd". :)
The other thing I don't understand is why you need to do that at all.
X11 programs are entirely capable of having their window be full-screen
size even after a standard xinit/startx startup, so I would think you wouldn't need to do a special startup to get full-screen, unless that's
an openttd issue.
-WBE
The other thing I don't understand is why you need to do that at all.
X11 programs are entirely capable of having their window be full-screen
size even after a standard xinit/startx startup, so I would think you
wouldn't need to do a special startup to get full-screen, unless that's
an openttd issue.
The issue may be with my .xinitrc invoking the window manager,
apparently that was not there before (AND I used a different
window manager).
I previously wrote in this thread:
The other thing I don't understand is why you need to do that at all.
X11 programs are entirely capable of having their window be full-screen
size even after a standard xinit/startx startup, so I would think you
wouldn't need to do a special startup to get full-screen, unless that's
an openttd issue.
[or, as you've correctly pointed out, a window manager issue ...]
to which Louis Epstein <le@lekno.ws> writes:
The issue may be with my .xinitrc invoking the window manager,
apparently that was not there before (AND I used a different
window manager).
I'd be surprised if it has anything to do with .xinitrc, but not
surprised if some window manager has an always-on-top bar of some kind.
twm, for example, does not. As Gerhard indicated, window managers
that have tool bars may also have a way of getting rid of it, or at
least of disabling its always-on-top property.
-WBE
The other thing I don't understand is why you need to do that at
all. X11 programs are entirely capable of having their window be
full-screen size even after a standard xinit/startx startup, so I
would think you wouldn't need to do a special startup to get
full-screen, unless that's an openttd issue.
The issue may be with my .xinitrc invoking the window manager,
apparently that was not there before (AND I used a different
window manager).
I'd be surprised if it has anything to do with .xinitrc, but not
surprised if some window manager has an always-on-top bar of some
kind. twm, for example, does not. As Gerhard indicated, window
managers that have tool bars may also have a way of getting rid of
it, or at least of disabling its always-on-top property.
I used fvwm2 before and this time it's xfce4.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 149:58:19 |
| Calls: | 10,383 |
| Files: | 14,054 |
| Messages: | 6,417,784 |