Fullscreen mode broken on a mac

[flaimo]

tried the jar file, as also the mac package. behavior is the same (after upgrading from earlier stable 4064. when i start the program, it starts in some kind of full screen mode, but there are no menubars. expose doesn't work anymore in that state either. clicking on the download button doesn't do anything. all i can do is press cmd-q to quit the program. i still think it would be better to disable this function on a mac completely because of the missing menubar.

4064 worked normally.

[flaimo]

video: ​http://cl.ly/0b1g463n0h0h3a2J1u3A

mac version is 10.6.8 with the latest java updates

[flaimo]

i downgraded back to 6064. this version still works.

[stoecker]

Seems like you somehow activated fullscreen mode. This was broken in previous version so you may not have noticed it.

• How does new JOSM version work with clean preferences?
• Does pressing <F11> (I hope I remember right the hotkey, you can look at 4064 menu to be sure) fix the issue?

[Xapitoun]

I have a same problem. When I click the preferences icon or an another menu, I select it but after Josm is blocked. Nothing is happens. I can only use «Echap» hotkey to unblock.

Xavier

[stoecker]

Does a fresh installation help? There have been no real changes regarding mac. The only things which may affect this seems to be the fixes in broken fullscreen mode.

Can you try older version between 4064 and 4201 (see download and download/Archiv) and tell after which version it first appears? Simply call them directly using "java -jar filename" instead of the all-in-one installation archive of Mac tested.

[skyper]

You can also try (as a workaround):

java -jar filename --maximize

or

java -jar filename --no-maximize

The first one works for me on a Linux (LDX + openbox) where JOSM always lies under the top panel (just tested still the same).
By the way, the second one produces a window which goes beyond my screen)

Good luck.

[stoecker]

Fullscreen mode and maximize are two different things!

[anonymous]

Here is a workaround: upon JOSM startup, click on View menu, choose "Fullscreen View," UNchecking it, and restoring your Mac OS X menu. You only need to do this once, as the setting is retained between JOSM launches.

[flaimo]

@anonym: there is no menubar in fullscreen mode on a mac (see the video i linked to).

[flaimo]

Shift+fn+F11 seems to do the trick. though the full screen mode doesn't show any menubar, which make this mode useless on a mac. mac user don't use full screen modes, since most native apps don't support that feature anyway, though that might change with os x lion.

@xapitoun: please verify that yours is the same problem by trying out Shift+fn+F11

[anonymous]

Right, flaimo, my workaround simply turns off Fullscreen View. When the Mac OS X menubar re-appears (from having turned off Fullscreen), this defect vanishes. Fullscreen mode on Mac OS X is ill-advised on Mac OS X for this reason, and so just "not using it" with JOSM is the correct thing to do. I do not advocate platform-specific code in Java apps, so I don't think that Fullscreen should be "disabled" if it were to be determined (by the running JOSM) that is it is running on Mac OS X, so I believe the correct answer here is "just don't use Fullscreen with a Mac, and if you ARE using it, disable it with View -> Fullscreen View (off) or perhaps Shift+Fn+F11.

[stoecker]

Currently fullscreen is not supported on Windows. Should we turn it off for MacOs as well?

[stoecker]

I had a look and fullscreen mode should not be available for MacOS at all. When you start JOSm from commandline, are there outputs like:

• Your operating system has no name, so I'm guessing its some kind of *nix.
• I don't know your operating system '...', so I'm guessing its some kind of *nix.

If yes, what are they exactly?

[flaimo]

we should do a quick survey in the forums and on the mailinglist who uses this feature. if hardly anyone is using this feature (it can't be windows or mac users), then maybe it would make sense to drop that functionality all together.

[stoecker]

Should be fixed in r4203.