On 8/31/05, Byron Ellis <[EMAIL PROTECTED]> wrote:
> There's definitely something a bit strange going on. The arguments as
> passed to wireframePanelCalculations from the code snippet show only
> 6060 elements for the z vector (51,101,16 respectively for x,y,rot)
> while the function routinely trie
There's definitely something a bit strange going on. The arguments as
passed to wireframePanelCalculations from the code snippet show only
6060 elements for the z vector (51,101,16 respectively for x,y,rot)
while the function routinely tries to access at positions in the z
vector >20,000...
On 29/ago/05, at 10:35, Prof Brian Ripley wrote:
> It does not crash for me on either Windows or Linux, but it does
> take a
> long time and the plot is a mess, so there does seem to be a
> lattice-related problem (maybe a usage one).
>
> However, I think the crash is a Mac (presumably quartz()
On Monday 29 August 2005 03:35, Prof Brian Ripley wrote:
> It does not crash for me on either Windows or Linux, but it does take a
> long time and the plot is a mess, so there does seem to be a
> lattice-related problem (maybe a usage one).
It is improper (or at least unanticipated) usage. The exa
It does not crash for me on either Windows or Linux, but it does take a
long time and the plot is a mess, so there does seem to be a
lattice-related problem (maybe a usage one).
However, I think the crash is a Mac (presumably quartz()) problem.
On Mon, 29 Aug 2005, stefano iacus wrote:
> This
This segfaults on OS X (10.4) on both X11 and quartz devices.
Seems a problem with lattice but I cannot test on other platforms
stefano
Begin forwarded message:
> From: "G. Sawitzki" <[EMAIL PROTECTED]>
> Date: 28 agosto 2005 14:11:18 GMT+02:00
> To: [EMAIL PROTECTED]
>
>
> Dear Stefano,
>
> th
