Automatic script structure validation shows a warning on opening the example script "

[NewsArchive]

Hi Friedrich,

I just open your example Script "asinvoker.sb7" and SB shows me a
warning, that the file is inconsitent. Is this a problem with the
example script or with your changed script validation?

Markus

[NewsArchive]

Hi Markus,

> I just open your example Script "asinvoker.sb7" and SB shows me a warning,
> that the file is inconsitent. Is this a problem with the example script or
> with your changed script validation?

The latest Examples Package should not give you this warning. Are you using
the "old" examples?

Friedrich

[NewsArchive]

OK, I see, you have updated the example files this morning... It's OK
now. Thank you.

Markus Zander

[NewsArchive]

Hi Markus,

> OK, I see, you have updated the example files this morning... It's OK now.
> Thank you.

Thank you for all your help!!

Friedrich

[NewsArchive]

I receievd this message when opening any existing SB7 script with new release.

PDF attached with windows that were displayed.

Mike

[NewsArchive]

Mike,

>I receievd this message when opening any existing SB7 script with new
>release.
>
> PDF attached with windows that were displayed.

Yes, this is correct and expected. The new SB75 can detect "conversion"
errors and fix it for you.

You can disable this check (Options | General Tab | Skip 'Script Structure
Validation'), but that's not recommended.

Friedrich

[NewsArchive]

Friedrich,

> Yes, this is correct and expected. The new SB75 can detect "conversion"
> errors and fix it for you.

You might want to make the messages a bit more descriptive and also
note that selecting YES won't mangle your script!<g>

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
RPM Review........: http://www.clarionmag.com/cmag/v11/v11n06rpm.html
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Enhanced Reporting: http://www.cpcs-inc.com


Product Release & Update Notices
http://twitter.com/DeveloperPLUS

[NewsArchive]

Hi Lee,

> You might want to make the messages a bit more descriptive and also
> note that selecting YES won't mangle your script!<g>

Yes, the "script" itself is not touched. All SB5 and SB6 converted projects
miss some SB7 specific properties and this might cause problems (e.g.
uninstall not being created). SB7 created projects are not affected.

Selecting "Yes" will repair the project by adding the missing properties.

Friedrich

[NewsArchive]

I was a little nervous when I got this too. I just clicked YES and
trusted Friedrich. :)

I then got 2 errors on the compile. Seems this new version catches
variables not all in upper case.

bob Roos

[NewsArchive]

What happened to them on the previous version/ Were they ignored with
no message or was the correct value subsitituted?

Bob roos

> Seems this new version catches variables not all in upper case.

[NewsArchive]

Hi Bob,

> What happened to them on the previous version/ Were they ignored with no
> message or was the correct value subsitituted?
>
>> Seems this new version catches variables not all in upper case.

The compiler has been enhanced in SB75. Some functions did not (correctly)
check for undefined runtime and compiler variables in the past.

In the Shortcut's "Target" and "Working directory" entries you had:

....\%Vendor%\%ProductName%...

instead of:

....\%VENDOR%\%PRODUCTNAME%...

In all SB versions prior V7.5, the compiler did not detect this problem in
your Shortcuts and as a result, your installer did not resolve the variables
at runtime.

Friedrich

[NewsArchive]

That is what I wanted to know. So I need to get a new distribution out
there because the path is not resolved correctly.

Bob Roos

> and as a result, your installer did not resolve the variables at runtime.