topic Re: Is there a way to suppress warning messages in a GDL scr in Libraries & objects

Is there a way to suppress warning messages in a GDL script?

Eric Bobrow — Sat, 03 Jul 2010 19:24:01 GMT

I am creating an object that will show samples of all the materials defined in a project.

To do this, I plan to use a simple loop statement that increments an index value, then tests to see if a material exists for that index using the statement:

n=REQUEST ("Name_of_material", index, name)

I tried this, and can see that variable n is 0 when there is no material with that index, while it is 1 when a material exists.

However, when the index is not associated with a material, a warning dialog comes up stating "Material not found at line 2 in 3D script of..."

Is there a way to suppress this warning message? I know that a user can turn off error messages in general, and then will only get a single message stating "there were errors", but that's not acceptable in this case.

Alternatively, is there a way to automatically fill an array with a list of index values for materials, similar to the special request available for a list of font names?

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Tue, 06 Jul 2010 23:06:47 GMT

Hello,

I do not know if this is usable, but this code makes a sorted value list of the material names - beginning with the given character. The looping would be better with do...while or similar, but just making a "quick one" this time.

You need to have a string type parameter named "materials" in addition to the value or master script code below.

(The array sorting code is borrowed from Frank Beister or Joachim Suehlo years ago, thanks to those gurus).


!--define arrays
dim s[], t[]

!--loop thru materials
for xx=1 to 255
	dummy= REQUEST ("Name_of_material", xx, name)
	if dummy & (strsub(materials,1,1) = strsub(name,1,1)) then
		n= n+1
		t= name
	endif
next xx


!--array sorting
for i=1 to vardim1(t)
	s= ""
next i

for i=1 to vardim1(t)
	p=i
	for j=1 to i-1
		if s>t then
			for k=i to j+1 step -1
				s=s[k-1]
			next k
			p=j : j=vardim1(s)
		endif 
	next j
	s=t 
next i


!--deliver the value list
values "materials" s, custom

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Tue, 06 Jul 2010 23:20:19 GMT

Hello,

A little modification; the same code with a word search function.


!--define arrays
dim s[], t[]

!--loop thru materials
for xx=1 to 255
	dummy= REQUEST ("Name_of_material", xx, name)
	if dummy & strstr(name, materials) then
		n= n+1
		t= name
	endif
next xx


!--array sorting
for i=1 to vardim1(t)
	s= ""
next i

for i=1 to vardim1(t)
	p=i
	for j=1 to i-1
		if s>t then
			for k=i to j+1 step -1
				s=s[k-1]
			next k
			p=j : j=vardim1(s)
		endif 
	next j
	s=t 
next i

!--deliver the value list
values "materials" s, custom

Hope this helps.

Regards, Juha

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Tue, 06 Jul 2010 23:32:21 GMT

Juha -

Thanks for the extensive code samples. I had already worked out a way to sort the materials by name, so this was not the main question. I do like how you create the arrays and then make a value list for a materials popup.

My main question is how to avoid getting an error message during execution of the script when the index does not have a defined material. This happens for me when the statement:

n=REQUEST ("Name_of_material", index, name)

is executed, and you have a similar statement in your script as you loop through to collect the material names. Do you get error messages when your script is executed?

Eric

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Wed, 07 Jul 2010 05:10:26 GMT

Hello Eric,

Now I understand - yes the looping gives an error. I checked other possibilities and seems that REQUEST{2} behaves better.

I made an extra checking here.




!--define arrays
dim s[], t[]

!--loop thru materials
for xx=1 to 255
	test= REQUEST{2}("Material_info", xx, "gs_mat_surface_rgb", r, g, b)
	if test then
		dummy= REQUEST("Name_of_material", xx, name)
		if strsub(materials,1,1) = strsub(name,1,1) then
			n= n+1
			t= name
		endif
	endif
next xx


!--array sorting
for i=1 to vardim1(t)
	s= ""		!--for numbers-->0 | for strings-->""
next i

for i=1 to vardim1(t)
	p=i
	for j=1 to i-1
		if s>t then
			for k=i to j+1 step -1
				s=s[k-1]
			next k
			p=j : j=vardim1(s)
		endif 
	next j
	s=t 
next i

!--deliver the value list
values "materials" s, custom

Hope this helps.

Best Regards, Juha

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Wed, 07 Jul 2010 06:40:30 GMT

Thank you!
The REQUEST{2} test works perfectly, allowing one to test whether an index number is valid before requesting the material name for that index.

I greatly appreciate your assistance.

Now, I have one other question...

I would like to show the material texture directly on plan, but am having problems with the script syntax, and the GDL manual documentation isn't very helpful.

My script currently is creating an array of little square slabs that each have a different material, and they show beautifully in 3D. In 2D, I'm using the following statement to show the squares on plan:

project2{2} 3,270,3+1024

This is crude, but gives a quick preview of the squares with a simple color based on the material, but it does not use the actual texture files of the materials.

I'd like to create temporary Symbol Fill definitions in the 2D script, and then run my loop to draw my little squares in 2D instead of using the Project2 statement. I have coded the following two lines - the first one queries the material texture file name and size, then the second one attempts to create a new Image Fill definition:

n=REQUEST{2} ("Material_info", "07 | Spanish Tile", "gs_mat_texture", file_name, w, h, mask, alpha)
DEFINE IMAGE_FILL "TestFill" file_name, fillTYPES_MASK 2, 85, 255, 136, 255, 34, 255, 136, 255, h, w, 0, 0

However, when I use the Check Script button, I get a syntax error for the second line that says "String type expression required at line 7..." I don't know what my error is - can you try this and let me know what I'm doing wrong?

Thanks again, in advance, for your help!

Eric

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Wed, 07 Jul 2010 07:56:19 GMT

Juha -
Just a quick note - I first posted a short reply thanking you for your help. Then I went back and edited my post to add another question.
Since I'm not sure whether you'd get another notification about the edited post, I'm adding this extra "reply" to make sure you know that I have another question that I hope you can help me with!
Eric

Re: Is there a way to suppress warning messages in a GDL scr

ztaskai — Thu, 08 Jul 2010 12:21:00 GMT

Eric wrote:
... when I use the Check Script button [with DEFINE IMAGE_FILL], I get a syntax error for the second line that says "String type expression required at line 7..." I don't know what my error is - can you try this and let me know what I'm doing wrong?

Hi Eric,

I'm afraid you found an annoying bug in the DEFINE IMAGE_FILL command. AC doesn't accept a string type variable as the file name, only a constant string expression in quotes. I can't think of any workaround. I entered this as a bug in GDL and I think the fix can get into a v14 hotfix.

I'm sorry you have to wait for the solution.

Best regards,

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Thu, 08 Jul 2010 14:54:46 GMT

Zsolt -
Wow! Did this bug exist in AC13? Is this the first time this bug has been reported?
I hope we don't have to wait too long for a hotfix...
Thanks for letting me know that it's a bug rather than user error!
Eric

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Thu, 08 Jul 2010 19:52:35 GMT

Hello Eric,

This might be worth trying;

- make a new string type parameter "pict" and make it a table with one cell

- put the file_name into that table with "parameters" command before using it

- use a new, just invented command: SET IMAGE_FILL



n=REQUEST{2} ("Material_info", "Testing Material", "gs_mat_texture", file_name, w, h, mask, alpha)
parameters pict[1]= file_name
DEFINE IMAGE_FILL "Testing" pict[1], 255, 255, 255, 255, 255, 255, 255, 255, w, h, 0, 0

set IMAGE_FILL "Testing"
poly2_ 4, 1+2+4+8,
	0, 0, 0,
	a, 0, 0,
	a, b, 0,
	0, b, 0

It works for me, hopefully for you too.

Best Regards; Juha

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Thu, 08 Jul 2010 22:21:25 GMT

Juha -

I tried your code, and was only partly successful. It does not generate an error message, but the value the script assigns for the pict[1] cell does not seem to be picked up properly.

I set the initial value for pict[1] to be "abc", then in the script assigned it to the value returned in the variable file_name.

When assigning this using the "parameters" option (as you suggested):

parameters pict[1]= file_name

the value is not picked up.

I verified this using the following line:

print "pict value= ", pict[1], ", ", file_name

which results in this message:

pict value= abc, Terracotta roof tile

When I take off the "parameters" option:

pict[1]= file_name

then the script generates an error (like it did earlier):

String type expression required at line 11 in the 2D script of file AMT Material Matrix.gsm.

As a last resort, I tried using both lines (the two variations of the pict[1]= statement, one with "parameters" and the other without), and still couldn't get it to work.

So, I am at a loss. If you have any ideas, please let me know!

Eric

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Fri, 09 Jul 2010 06:12:36 GMT

Hello Eric,

I wonder if you have the code in the master script? At least the
first part;


!--master script
n=REQUEST{2} ("Material_info", "Testing Material", "gs_mat_texture", file_name, w, h, mask, alpha) 
parameters pict[1]= file_name 
DEFINE IMAGE_FILL "Testing" pict[1], 255, 255, 255, 255, 255, 255, 255, 255, w, h, 0, 0

The second part can be in the master or 2D script


!--master or 2D script
set IMAGE_FILL "Testing" 
poly2_ 4, 1+2+4+8, 
   0, 0, 0, 
   a, 0, 0, 
   a, b, 0, 
   0, b, 0

I tested again and works nicely here.

Best Regards, Juha

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Fri, 09 Jul 2010 08:46:43 GMT

Juha -

Thank you for your suggestions. Based on your idea, I created an object that draws an Image Fill in 2D based on the texture image file for any material chosen parametrically. I then adapted my original matrix part to call the new object repeatedly, once for each material swatch sample.

Unfortunately, although the new object will draw appropriate textures when placed on the floor plan, when it is called from the matrix object, the parameters assignment statement isn't working. I don't know if this is a bug, or if it is a limitation in the way that PARAMETERS statements work in the master script. (I tried placing some or all of the code into the Parameter Script, but couldn't get it to work at all.)

Here is my Master Script, which has a print statement included for testing purposes:

n=REQUEST{2} ("Material_info", materialtype, "gs_mat_texture", file_name, w, h, mask, alpha)
parameters pict[1]= file_name
print "materialtype=",materialtype," file_name=",file_name,", pict[1]=",pict[1]
DEFINE IMAGE_FILL "newimagefill" pict[1], 255, 255, 255, 255, 255, 255, 255, 255, w, h, 0, 0

When I ran a small loop with my matrix object, which called the simple object once for each material, I got the following report:

materialtype= 73 file_name=Brick Common Flemmish alpha, pict[1]=Brick Running alpha
materialtype= 72 file_name=Brick English alpha, pict[1]=Brick Running alpha
materialtype= 70 file_name=Brick Surface alpha, pict[1]=Brick Running alpha
materialtype= 71 file_name=Stucco alpha, pict[1]=Brick Running alpha
materialtype= 74 file_name=Tiles Wall alpha, pict[1]=Brick Running alpha

You can see that each time the object was called, it received a different materialtype as a parameter from the matrix object. The file_name variable successfully picks up the proper texture file name, however the pict[1] string array variable is somehow not being set even though I am using the parameters statement as you did in the Master Script.

If you send me a private message with your email address, I'll send you a copy of the two GDL parts for you to see for yourself!

Re: Is there a way to suppress warning messages in a GDL scr

ztaskai — Fri, 09 Jul 2010 15:13:51 GMT

Hi Eric,

This bug was there in AC13 but not in AC12. I guess no one uses this in production. We tested it thoroughly when the command came to be, but now I see that we don't have a daily test for this one. So you're the first one to report it.

Thanks for bringing this to our attention and sorry again for the annoyance!

Regs,

Re: Is there a way to suppress warning messages in a GDL scr

Anonymous — Fri, 09 Jul 2010 20:42:52 GMT

Hello Eric,

Thanks for the email and the posted objects. Here is a general
piece of code where the textures react correctly. I stored the fill
and texture names in the "pict" parameter table and picked them
for 2D plan from there. Seems to work.

I post it here just in case someone finds it useful, therefore I added
some comments too.

As before a string type parameter "pict" is needed, it is made
a table with two columns -> pict[1][1]

This is a master script:



!--stretching the table
for xx=1 to 255
	parameters pict[xx][1]="", pict[xx][2]=""
next xx

!--looping thru materials
for xx=1 to 255
	test= REQUEST{2}("Material_info", xx, "gs_mat_surface_rgb", r, g, b)

	if test then!<--we have a material with index xx

		dummy= REQUEST("Name_of_material", xx, name) 
		file_name= ""
		n=REQUEST{2} ("Material_info", name, "gs_mat_texture", file_name, w, h, mask, alpha)
		nr= nr+1

		if file_name#"" then!<--we have a material with a texture --- store the fill name and the texture name, define image fill

			fill_name= name
			parameters pict[nr][1]= fill_name, pict[nr][2]= file_name
			DEFINE IMAGE_FILL pict[nr][1] pict[nr][2], 255, 255, 255, 255, 255, 255, 255, 255, w, h, 0, 0

		else!<--we have a material but no texture --- store just the fill name

			parameters pict[nr][1]= name, pict[nr][2]= ""

		endif
	endif
next xx



!--just limiting a stretching hotspot values
values "A" range[1,nr] step 1, 1

This is a 2D script:



hotspot2 0, 0
hotspot2 a, 0

!--looping thru stored materials
for xx= 1 to vardim1(pict)

	if pict[xx][2]#"" then!<--we have an image fill

		set IMAGE_FILL pict[xx][1]!<--get the mage fill name
		poly2_ 4, 1+2+4+8,
			0,   0, 1,
			1,   0, 1,
			1,	-1, 1,
			0,	-1, 1

  		!--texture matrix transformation  
		if dx<a-1 then
			add2 1, 0
			dx= dx+1
		else
			add2 -a+1, -1
			dx= 0
		endif
		nt=nt+1

	endif

next xx
del nt

Best Regards, Juha

Re: Is there a way to suppress warning messages in a GDL scr

Eric Bobrow — Sat, 10 Jul 2010 07:38:50 GMT

Thank you!
I haven't had a chance to test it out, but it looks great.
Eric