Ronnie,
Just curious; what version and platform? I've been using GoLive 6.0 W2KPro with LP5 Developer Edition and have not experienced any problems.

Many thanks,
John

-----Original Message-----
From: Ronnie R. Higgins Jr. [mailto:lasso@whitedragon.com]
Sent: Sunday, June 15, 2003 3:05 PM
To: lassostudio@lists.blueworld.com
Subject: agl:translated - REVISITED

I've spent this week dealing with GoLive's incorrect translation of
some of the Lasso code it interprets. For reference, this is code
written in Source mode then is rewritten by GoLive with the
<agl:translated> tag when switching to Layout mode.

I have read the messages (like #2296) and Support Central Article
(http://support.blueworld.com/article.lasso?id=12202002707). Blue World
states this is entirely "cosmetic". With respect, I'm going to disagree
and state my case below.

The following three tests will change the background color of a table
cell based on a conditional statement.

>> This works and is not translated by GoLive.
[Var: 'myVar'='TEST']
<table>
<tr>
<td bgcolor="[If: $myVar == 'TEST']#006400[Else]#FF0000[/If]">Test
Cell 1</td>
</tr>
</table>

>> This works in Source mode before being translated by GoLive.
[Var: 'myGoodArray'=(Array: 'TEST')]
<table>
<tr>
<td bgcolor="[If:(Var: 'myGoodArray')->Find: 'TEST' != (array) ||
(Var: 'myGoodArray')->Find: 'BLAH' !=
(array)]#006400[Else]#FF0000[/If]">Test Cell 2</td>
</tr>
</table>

>> This is the code from above after being translated by GoLive. It
does not work properly.
[Var: 'myBadArray'=(Array: 'TEST')]
<table>
<tr>
<td bgcolor="<agl:translated classid="ls_cls_inspector"
orig="[If:(Var: 'myBadArray')-
>Find: 'TEST' != (array) || (Var: 'myBadArray')-
>Find: 'BLAH' != (array)]"><ls_img right="Left Bracket.gif"
image="Condition Tag.gif"
left=""/></agl:translated>#006400[Else]#FF0000[/If]">Test Cell 3</td>
</tr>
</table>


I've used Lasso code within table parameters many times, this is the
first I've tried to use an array. It would seem that GoLive doesn't
mind conditionals, nor variables, but doesn't care for member tags. In
my code (not this test) I use a more complex conditional statement that
is so mangled, errr, interpreted by GoLive that it causes a Lasso
syntax error and can't load the page.

Hopefully Blue World will concur with this and we can get Adobe to fix
a bug, not ignore a "cosmetic" issue. An issue which has been noted
since late 2002.

For the record, I'm using Lasso Pro 6.0.4, Lasso Studio 6.0.1, GoLive
6.0.1, Mac OS X 10.2.6

Best ... Ronnie R. Higgins Jr.
White Dragon Consulting


#############################################################
Archives:<http://www.listsearch.com/lassostudiotalk.lasso>
This message is sent to you because you are subscribed to
the mailing list <lassostudio@lists.blueworld.com>.
To unsubscribe, E-mail to: <lassostudio-off@lists.blueworld.com>
To switch to the DIGEST mode, E-mail to <lassostudio-digest@lists.blueworld.com>
To switch to the INDEX mode, E-mail to <lassostudio-index@lists.blueworld.com>
Send administrative queries to <lassostudio-admin@lists.blueworld.com>

#############################################################
Archives:<http://www.listsearch.com/lassostudiotalk.lasso>
This message is sent to you because you are subscribed to
the mailing list <lassostudio@lists.blueworld.com>.
To unsubscribe, E-mail to: <lassostudio-off@lists.blueworld.com>
To switch to the DIGEST mode, E-mail to <lassostudio-digest@lists.blueworld.com>
To switch to the INDEX mode, E-mail to <lassostudio-index@lists.blueworld.com>
Send administrative queries to <lassostudio-admin@lists.blueworld.com>