Fri, Oct 10 2003
00:01:04
|
|
Request created by guest
|
|
Subject: VRML 1.0 export
Platform: other (dual-G4 / MacOSX 2)
grass obtained from: Other (CDROM etc) (OpenOSX)
grass binary for platform: Downloaded precompiled Binaries
GRASS Version: 5.0.2
The VRML 1.0 export is not working well. The mesh producted is not standard VRML.
It
adds a ' , ' after the last Coordinate3 point description. Same for the last
IndexedFaceSet : should be "a,b,c,-1" and not "a,b,c,-1,"
Yann |
|
Sun, Oct 12 2003
15:21:31
|
|
Mail sent by paul-grass@stjohnspoint.co.uk
|
|
Return-Path |
<paul-grass@stjohnspoint.co.uk>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Sun, 12 Oct 2003 14:21:27 +0100 (BST)
|
From |
Paul Kelly <paul-grass@stjohnspoint.co.uk>
|
X-X-Sender |
paulk@agrippa.ukshells.co.uk
|
To |
Request Tracker <grass-bugs@intevation.de>
|
Cc |
grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #2152] (grass) VRML 1.0 export
|
In-Reply-To |
<20031009220104.B2A6F13B9E@lists.intevation.de>
|
Message-ID |
<Pine.LNX.4.53.0310121418360.9789@agrippa.ukshells.co.uk>
|
References |
<20031009220104.B2A6F13B9E@lists.intevation.de>
|
MIME-Version |
1.0
|
Content-Type |
MULTIPART/MIXED; BOUNDARY="182016655-251752898-1065964887=:9789"
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=5.0 tests=BAYES_00
|
X-Spam-Level |
|
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Send mail to mime@docserver.cac.washington.edu for more info.
--182016655-251752898-1065964887=:9789
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Fri, 10 Oct 2003, Request Tracker wrote:
> The VRML 1.0 export is not working well. The mesh producted is not standard
VRML. It
> adds a ' , ' after the last Coordinate3 point description. Same for the last
> IndexedFaceSet : should be "a,b,c,-1" and not "a,b,c,-1,"
The attached patch to p.vrml would fix this (presumably the Material Color
section should have the same treatment). But I haven't had any problems
with the current output. Are there some readers the VRML output won't work
with? Can you give a link to somewhere describing the VRML standard that
shows it as you describe? Then we could apply the change to p.vrml
--182016655-251752898-1065964887=:9789
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="put_grid.c.diff"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.LNX.4.53.0310121421270.9789@agrippa.ukshells.co.uk>
Content-Description:
Content-Disposition: attachment; filename="put_grid.c.diff"
SW5kZXg6IHB1dF9ncmlkLmMNCj09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJD
UyBmaWxlOiAvZ3Jhc3NyZXBvc2l0b3J5L2dyYXNzL3NyYy9wYWludC9wLnZy
bWwxLjEvcHV0X2dyaWQuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMw0K
ZGlmZiAtdSAtcjEuMyBwdXRfZ3JpZC5jDQotLS0gcHV0X2dyaWQuYwkyMyBB
cHIgMjAwMiAyMDoyNTowMyAtMDAwMAkxLjMNCisrKyBwdXRfZ3JpZC5jCTEy
IE9jdCAyMDAzIDEzOjE3OjQ2IC0wMDAwDQpAQCAtNjAsNyArNjAsMTAgQEAN
CiAJCWlmIChHX2lzX2ZfbnVsbF92YWx1ZSAodGYpKSAqdGYgPSAwLjA7DQog
CQljb29yZHkgPSAqdGY7DQogCQlkb19jb29yZGNudigmY29vcmR5LCAneScp
Ow0KLQkJc3ByaW50ZihzdHIsIiVmICVmICVmLCIsIGNvb3JkeCwgY29vcmR5
LCBjb29yZHopOw0KKwkJc3ByaW50ZihzdHIsIiVmICVmICVmIiwgY29vcmR4
LCBjb29yZHksIGNvb3Jkeik7DQorCQlpZiAoKHJvdyA8IChyb3dzLTEpKSB8
fCAoY29sIDwgKGNvbHMtMSkpKQ0KKwkJICAgIC8qIE5vIGNvbW1hIGFmdGVy
IGxhc3QgcG9pbnQgKi8NCisJCSAgICBzdHJjYXQoc3RyLCIsIik7DQogCQl2
cm1sX3B1dGxpbmUoMCx2b3V0LHN0cik7DQogCQl0ZisrOw0KIAkgICAgfQ0K
QEAgLTEwMSw4ICsxMDQsMTEgQEANCiAJICAgIEdfbG9va3VwX2ZfcmFzdGVy
X2NvbG9ycyAodGYsIHJlZCwgZ3JlZW4sIGJsdWUsIHNldCwgY29scywgY29s
cik7DQogDQogCSAgICBmb3IoY29sPTA7IGNvbCA8IGNvbHM7IGNvbCsrKXsN
Ci0JCXNwcmludGYoc3RyLCIlLjNmICUuM2YgJS4zZiwiLCANCisJCXNwcmlu
dGYoc3RyLCIlLjNmICUuM2YgJS4zZiIsIA0KIAkJCXJlZFtjb2xdLzI1NS4s
IGdyZWVuW2NvbF0vMjU1LiwgYmx1ZVtjb2xdLzI1NS4pOw0KKwkJaWYgKChy
b3cgPCAocm93cy0xKSkgfHwgKGNvbCA8IChjb2xzLTEpKSkNCisJCSAgICAv
KiBObyBjb21tYSBhZnRlciBsYXN0IHBvaW50ICovDQorCQkgICAgc3RyY2F0
KHN0ciwiLCIpOw0KIAkJdnJtbF9wdXRsaW5lKDAsdm91dCxzdHIpOw0KIAkg
ICAgfQ0KIAl9DQpAQCAtMTM1LDkgKzE0MSwxMiBAQA0KIAkgICAgZm9yKGNv
bD0wOyBjb2wgPCBjb2xzLTE7IGNvbCsrKXsNCiAJCWMxID0gcm93KmNvbHMr
Y29sOw0KIAkJYzIgPSBjMSArIGNvbHMgKzE7DQotCSAgICAgICAgc3ByaW50
ZihzdHIsIiVkLCAlZCwgJWQsIC0xLCAlZCwgJWQsICVkLCAtMSwiLA0KKwkg
ICAgICAgIHNwcmludGYoc3RyLCIlZCwgJWQsICVkLCAtMSwgJWQsICVkLCAl
ZCwgLTEiLA0KIAkJYzEsIGMxK2NvbHMsIGMxKzEsIA0KIAkJYzIsIGMyLWNv
bHMsIGMyLTEgKTsNCisJCWlmICgocm93IDwgKHJvd3MtMikpIHx8IChjb2wg
PCAoY29scy0yKSkpDQorCQkgICAgLyogTm8gY29tbWEgYWZ0ZXIgbGFzdCBw
b2ludCAqLw0KKwkJICAgIHN0cmNhdChzdHIsIiwiKTsNCiAJCXZybWxfcHV0
bGluZSgwLHZvdXQsc3RyKTsNCiAJICAgIH0NCiAJfQ0K
--182016655-251752898-1065964887=:9789--
|
|
Sun, Oct 12 2003
18:46:54
|
|
Mail sent by coffeehouse@free.fr
|
|
Return-Path |
<coffeehouse@free.fr>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Sun, 12 Oct 2003 18:46:08 +0200
|
Subject |
Re: [bug #2152] (grass) VRML 1.0 export
|
Content-Type |
text/plain; charset=US-ASCII; format=flowed
|
Mime-Version |
1.0 (Apple Message framework v552)
|
From |
Yann Bouschet <coffeehouse@free.fr>
|
To |
Paul Kelly via RT <grass-bugs@intevation.de>
|
Content-Transfer-Encoding |
7bit
|
In-Reply-To |
<20031012132131.C495A13B99@lists.intevation.de>
|
Message-Id |
<945B3E1A-FCD3-11D7-81E4-000393C48960@free.fr>
|
X-Mailer |
Apple Mail (2.552)
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=5.0 tests=BAYES_00
|
X-Spam-Level |
|
>> The VRML 1.0 export is not working well. The mesh producted is not
>> standard VRML. It
>> adds a ' , ' after the last Coordinate3 point description. Same for
>> the last
>> IndexedFaceSet : should be "a,b,c,-1" and not "a,b,c,-1,"
>
> The attached patch to p.vrml would fix this (presumably the Material
> Color
> section should have the same treatment). But I haven't had any problems
> with the current output. Are there some readers the VRML output won't
> work
> with? Can you give a link to somewhere describing the VRML standard
> that
> shows it as you describe? Then we could apply the change to p.vrml
some links :
(in french) - http://raphaello.univ-fcomte.fr/IG/Vrml/Vrml.htm
there's an example at 2/3 of this page
(in english) - http://webdocs.essex.ac.uk/vrml/vrml-1.0.html
by the end of the page see the example
- http://www.informatik.hu-berlin.de/Themen/vrml/vrmlspec.html
that's the same page as above but on a different website. I've found
other website with this specs page.
- http://www.vijaymukhi.com/vmis/vrml1.htm
here again, see the quick example at the end of the page
For the VRML readers, Corel Bryce 5 won't import it (parsing error)
I couldn't use the patch you attached, I don't know how to do...
Thanks anyway.
Yann Bouschet
--------------------------------------------
the CoffeeHouse
graphic design & communication
50, grand rue Jean Moulin
34000 Montpellier
tel : 04-67-66-13-34
http://coffeehouse.free.fr
--------------------------------------------
|
|
Sun, Oct 12 2003
20:42:26
|
|
Mail sent by glynn.clements@virgin.net
|
|
Return-Path |
<glynn.clements@virgin.net>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
From |
Glynn Clements <glynn.clements@virgin.net>
|
MIME-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Transfer-Encoding |
7bit
|
Message-ID |
<16265.41072.208325.987340@cerise.nosuchdomain.co.uk>
|
Date |
Sun, 12 Oct 2003 19:41:52 +0100
|
To |
Paul Kelly <paul-grass@stjohnspoint.co.uk>
|
Cc |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #2152] (grass) VRML 1.0 export
|
In-Reply-To |
<Pine.LNX.4.53.0310121418360.9789@agrippa.ukshells.co.uk>
|
References |
<20031009220104.B2A6F13B9E@lists.intevation.de> <Pine.LNX.4.53.0310121418360.9789@agrippa.ukshells.co.uk>
|
X-Mailer |
VM 7.07 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=5.0 tests=BAYES_00
|
X-Spam-Level |
|
Paul Kelly wrote:
> > The VRML 1.0 export is not working well. The mesh producted is not standard
VRML. It
> > adds a ' , ' after the last Coordinate3 point description. Same for the last
> > IndexedFaceSet : should be "a,b,c,-1" and not "a,b,c,-1,"
>
> The attached patch to p.vrml would fix this (presumably the Material Color
> section should have the same treatment). But I haven't had any problems
> with the current output. Are there some readers the VRML output won't work
> with? Can you give a link to somewhere describing the VRML standard that
> shows it as you describe? Then we could apply the change to p.vrmlIndex: put_grid.c
The VRML 1.0 standard explicitly permits a trailing comma:
http://www.web3d.org/technicalinfo/specifications/VRML1.0/index.html#Fields
Multiple-valued fields are written as a series of values
separated by commas, all enclosed in square brackets. If the
field has zero values then only the square brackets ("[]") are
written. THE LAST MAY OPTIONALLY BE FOLLOWED BY A COMMA. If
the field has exactly one value, the brackets may be omitted
and just the value written. For example, all of the following
are valid for a multiple-valued field containing the single
integer value 1:
[Emphasis mine.]
So, it's a bug in the viewer.
FWIW, VRML 97 is even more liberal; the comma is considered a
whitespace character.
--
Glynn Clements <glynn.clements@virgin.net>
|
|
Tue, Jun 19 2007
09:14:02
|
|
Status changed to resolved by hbowman
|
|
Tue, Jun 19 2007
09:14:02
|
|
Comments added by hbowman
|
|
bug in viewer, closing bug.
VMRL is better handled by *.out.vtk modules these days.
Hamish
|
|