Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Script in SIM not working - LSLForge.exe arguments error #16

Open
RayZopf opened this issue Feb 26, 2016 · 0 comments
Open

Running Script in SIM not working - LSLForge.exe arguments error #16

RayZopf opened this issue Feb 26, 2016 · 0 comments
Labels

Comments

@RayZopf
Copy link

RayZopf commented Feb 26, 2016

https://code.google.com/archive/p/lslforge/issues/37
Posted on Jan 12, 2014 by Happy Wombat
What steps will reproduce the problem? 1. open a script within LSL Project 2. choose Run as - Launch in LSL Sim 3. look at the given Console

What is the expected output? What do you see instead? A Sim should be started, the script should run - instead: LSLForge.exe: in element tag sim-descriptor, In a sequence: in element tag source_files, In a sequence: in element tag scripts, In a sequence: in element tag item, Missing opening bracket: Expected </ but found & in file input at line 1 col 8300

What version of the product are you using? On what operating system? LSLForge 0.16 eclipse.buildId=4.3.0.M20130911-1000 java.version=1.7.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.standard.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product Win 7 64bit

Please provide any additional information below. The col # the Missing sing appears differs from script to script (e.g. 8578 with the given Dialog example)

Comment 1

Posted on Jan 14, 2014 by Happy Wombat
identified the problem:

if a folder inside a LSLForge project holds "&" this will break Run/Debug execution it does not matter where inside the project this folder is ...

workaround: avoid special signs in any folder/file name if not possible, create another LSLForge project to use Run/Debug there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants