[Paraview] macbook paraview problem

[Ken Mankoff]

Your app (with or without icon) is the folder that ends in ".app". You
should be able to drag-and-drop that elsewhere and double-click,
although not if you have to set LD_LIBRARY_PATH.

  -k.

On 2014-05-12 at 14:37, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Ken, Thanks. I didn’t see your reply until now as it went into my spam
> folder but as I replied to the other Ken using the open method fixes the
> problem. I don’t have an app icon (where’s that?) - when I launch paraview
> I need to set a bunch of ld_library paths and plugin paths (for different
> builds and options) so a script which sets these up and then calls the
> open /bla/bla is ideal.
>
> JB
>
> On 12/05/14 14:29, "Ken Mankoff" <mankoff at gmail.com> wrote:
>
>>
>>If I launch the Kitware build of paraview the way you describe, I have
>>similar behavior, but a simple click on Paraview or CMD+TAB brings it to
>>the foreground. But if I launch it with "open /path/to/paraview.app" (or
>>a double-click on the App icon) then it opens in the foreground. Does
>>that help?
>>
>>  -k.
>>
>>On 2014-05-12 at 06:26, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
>>> Hello all,
>>>
>>> I have not used paraview much on a macbook until today - I'm having
>>>problems because after I have finished compiling paraview or some custom
>>>plugins, I run it by executing
>>> /Users/biddisco/build/pv4/bin/paraview.app/Contents/MacOS/paraview &
>>> from a terminal window, but although paraview appears and runs fine,
>>>the menu bar frequently does not appear and the terminal window menu
>>>stays at the top of the screen
>>> This makes paraview essentially useless as I can't create any sources,
>>>add filters etc etc.
>>>
>>> Sometimes I can make it appear by minimizing the terminal and moving
>>>focus back to paraview (But that is quite annoying)
>>>
>>> Is there some key magic step that is required for applications to make
>>>the menus appear on macs (or just an easier way)?
>>>
>>> thanks
>>>
>>> JB
>>