File.toString(int formatType)

[d.healey]

Those strings are constants, so you need to use File.Filename

[ulrik]

@d-healey

File.Filename

still shows the whole path

[ulrik]

@ulrik

File.NoExtension
&&
File.FullPath

is working, but

File.Filename || File.OnlyExtension

is not working, they both gives the full path

[d.healey]

@ulrik I seem to remember a while back we discovered a bug with the constants not returning the correct values - @Christoph-Hart

Each constant just returns a number 0, 1, 2, etc. so for Filename I guess you would use 3.

[ulrik]

@d-healey ahh, yes you’re right, I remember now, thank you David!

[d.healey]

Just want to give this a bump because these constants still don't work.

In fact none of them work now but I thought some of them did previously...

[Dan Korneff]

@d-healey Playing with them right now with files downloaded from a server. Here's what I'm seeing
.toString(0) = full file path
.toString(1) = filename (no extension)

Is that different than what you're looking for?

[d.healey]

@dustbro said in File.toString(int formatType):

Is that different than what you're looking for?

Try to print .toString(File.NoExtension); and you will get an undefined error.

[Dan Korneff]

@d-healey said in File.toString(int formatType):

.toString(File.NoExtension)

I don't think you can use anything except an integer for this function.

The integer is passed to the .toString function switch case.

[d.healey]

@dustbro Exactly but those constants should provide that integer so we don't have to use magic numbers

[Dan Korneff]

@d-healey Do any of the constants work? or are they all broken?

[d.healey]

@dustbro said in File.toString(int formatType):

@d-healey Do any of the constants work? or are they all broken?

These File ones seem to all be broken, but I don't think that's always been the case.

[Lindon]

@d-healey said in File.toString(int formatType):

@dustbro said in File.toString(int formatType):

@d-healey Do any of the constants work? or are they all broken?

These File ones seem to all be broken, but I don't think that's always been the case.

..its always been the case for me.

[ustk]

@d-healey @dustbro @Lindon Since the enum is part of the class ScriptFile, it is the reference of the file itself that you have to take for using the enum names, not the File API:

const var myFile =  FileSystem.getFolder(FileSystem.Desktop).getChildFile("myFile.txt");

Console.print(myFile.toString(myFile.NoExtension));

It is the same when you use, let's say a simple gain, it's the reference of the effect "myGain" you use to access the different parameters.
For instance myGain.Balance, not Synth.Balance

I know the location in FileSystem for instance are accessed through FileSystem.SpecialLocation,
but in this case, you use the API, not a reference of it that you have created (well, at least if I explain correctly :) )

[d.healey]

@ustk Oh that's right! Mystery solved, thanks :)