On Thu, Jan 12, 2012 at 07:06:48AM -0000, Johannes Ring wrote:
> The VTK version included in the OS X binary is not that old, but there
> might be a bug in VTK on OS X because both SetSize(int, int) and
> SetSize(int a[2]) are supposed to work. This can easily be fixed by
> modifying the file
>
> /Applications/FEniCS.app/Contents/Resources/lib/python2.6/site-
> packages/viper/viper.py
>
> on OS X 10.6 or
>
> /Applications/FEniCS.app/Contents/Resources/lib/python2.7/site-
> packages/viper/viper.py
>
> on OS X 10.7. Simply replace line 1299, that is
>
> renWin.SetSize(self.window_size)
>
> with this line
>
> renWin.SetSize(*self.window_size)
>
> This should work on all platforms so we might as well apply this fix
> in Viper.
On Thu, Jan 12, 2012 at 07:06:48AM -0000, Johannes Ring wrote: FEniCS. app/Contents/ Resources/ lib/python2. 6/site- viper/viper. py FEniCS. app/Contents/ Resources/ lib/python2. 7/site- viper/viper. py SetSize( self.window_ size) SetSize( *self.window_ size)
> The VTK version included in the OS X binary is not that old, but there
> might be a bug in VTK on OS X because both SetSize(int, int) and
> SetSize(int a[2]) are supposed to work. This can easily be fixed by
> modifying the file
>
> /Applications/
> packages/
>
> on OS X 10.6 or
>
> /Applications/
> packages/
>
> on OS X 10.7. Simply replace line 1299, that is
>
> renWin.
>
> with this line
>
> renWin.
>
> This should work on all platforms so we might as well apply this fix
> in Viper.
I've applied Johannes' fix in Viper.
Should we make a release of Viper 1.0.1?
--
Anders