My simple editor

[danbaron]

"File" --> "New", doesn't work.

If I save a file under a different name, the file name at the top of the screen does not always update.

A script will not execute, if it is in a folder which contains a space character in its name. I have a folder on my desktop called, "NEW THIN". Scripts in that folder will not run.

Otherwise, it works fast.


Dan

[zlatkoAB]

Yes Dan you are right.
I really dont know why that heapend?
Maby someone here can help to solve this problem...

[zlatkoAB]

Hello...
Im still waiting for answer about file path which my editor send to
thinbasic interpreter?
Is someone here who can explain me what is wrong with filename
which contain blank space like this
C:\My program.tbasic

Why thinBasic dont regognize this file as script?
as i say before i use command line like this:
"thinbasic.exe",filename

filename string in this case is 'C:\My program.tbasic'
So what is wrong ?

[Petr Schreiber]

Hi Zlatko,

it is common practice, that if path contains spaces, it should be surrounded by double quotes (in the string itself).

So instead of string:

C:\My program.tbasic

you should send:

"C:\My program.tbasic"

The reason to do so is that the part after space could be confused with other program parameter. Having it all in "" makes sure it will be took as single block.


Petr

[ErosOlmi]

Hi Zlatko,

it is not thinBasic but the operating system shell.
It is always good practice (like Petr said) to enclose file names parameter in double quote in order not to create confusion to the application expecting such data.

When you pass source code to be executed to thinBasic it also checks for additional parameters. Official syntax is the following:

thinBasic.exe <Script file name> [Optional parameters]

where <Script file name> should be enclosed in double quote otherwise part of the file name will be confused with [Optional parameters]

[Optional parameters] are parameters user can pass to the script in order to be used at runtime.

There are other parameters you can pass to thinBasic but till now I've not released them in help file. I will add in future in order for 3rd party programmers be able to better interact with thinBasic. Real command line syntax is something like:

thinBasic.exe [execution flags] <Script file name> [Optional parameters]

I will let you know more about [execution flags] this evening when back at home.

Ciao
Eros

[zlatkoAB]

Aha i see now...
Same problem i have with YaBasic editor to and i simply dont know
why that heapend.
OK ...
I will add double quotes and try.
Thanks again both of you!

Yes Eros,that would be fine that you tell me how look parametars
or like you say execution flags.

Zlatko

[zlatkoAB]

YES...
IT works fine now.
Code look like this:

filename=LTRIM$(RTRIM$(filename))
            'add double quote
            filename=chr$(34)+filename+chr$(34)
            'execute script
            SYSTEM Getstartpath+"thinBasic.exe",filename

Also i will add scintilla markers with SUB/END SUB
and with FUNCTION /ENDFUNCTION...

[ErosOlmi]

Here the [execution flags] you can use when using

thinBasic.exe [execution flags] <Script file name> [Optional parameters]

where [execution flags] can be one of the following

• @D
  Debug mode: the script will be executed in debug mode showing thinbasic debug window. Execution is retained by the debug engine until runtime error or user exiting from debugger.
• @O
  Obfuscation mode. The script will not be executed but an obfuscated version of the original script will be created in the same directory of the original script. Obfuscated scripts have .tbasicx extension. Execution will immediately return to calling program.
• @B
  Dependency mode. The script will be partially executed in order to analyse dependant module and include files. A file with the same file name of the original script but with extension .sdep will be created in the same directory or the original script. Execution will immediately return to calling program.

Ciao
Eros

[zlatkoAB]

Thanks Eros...