On 3/11/21 4:33 PM, Sean Cole (Pi) via use-livecode wrote:
> Mark,
> Give an example of what would be better, not just hit and run with a
> 'That's crap!' comment. Way to make me feel good for all the hard
work put
> in. THANKS BUDDY!
Sean-
Not intended to be a 'that's crap' comment. You've go
On Thu, 11 Mar 2021 at 23:31, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Sean-
>
> What happens when a folder or a file gets renamed?
>
The main purpose of me having an FileSystem Array *like this* was for DLT
or BluRay _archives_ of projects, so no file alterations wo
Mark,
Give an example of what would be better, not just hit and run with a
'That's crap!' comment. Way to make me feel good for all the hard work put
in. THANKS BUDDY!
Do better!
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit th
Sean & Others,
Wow.
I will be reading this over to learn all i can from it, and see how this
knowledge can help me be a better LC dev.
I have a funny feeling it will come in handy one day soon.
I very much appreciate the time it took to explain all this.
On Thu, Mar 11, 2021 at 6:32 PM Mark W
On 3/11/21 3:03 PM, Sean Cole (Pi) via use-livecode wrote:
I hope that all makes sense.
Sean-
That makes sense, but it's a bad paradigm (IMO) for the same reason that
using real data for database indexes is a bad idea unless it just gets
written once and doesn't need maintenance.
What hap
Sorry, I just wanted to add...
The keys of tTableA["c:/"] would be:
.FileC
.FileC,Date
.FileC,Kind
.FileC,Size
Folder1
Folder1,Date
Folder1,Kind
Folder1,Size
...
Folder4
Folder4,Date
Folder4,Kind
Folder4,Size
An alternative for "Kind" could be ("
On to Array use for File System Indexing:
Take a simple FS structure:
c:/
.FileC
Folder1
File1.txt
Folder2
Size (aka Folder2_1)
File2.txt
File2_1.png
Folder3
Folder4
Archive.zip
File4.doc
Say we want to store in our indexin
Richard and Bob
Correct! In everything you say. [x,y,z] is, in LC space, a single
dimensional space and especially about use case. But then you are limiting
yourself to single dimensional thinking. Here is my next point that I was
coming to, so well done for preempting me.
Going back a bit, in a
A well put answer to that egregious question that haunts ALL who are problem
solvers: “Which is better?”
A person might mean, better for your pocketbook, Long term/short term, better
to configure, better performance, better support, better looking, better
sounding...
Really, this is a perennia
Sean Cole wrote:
> Why is tArray[x,y,z] more useful/flexible but not better
> than tArray[x][y][z]?
Is it?
Remember the definition of an array: a collection of name-value pairs
where the name can be any string up to 255 chars long, and the value can
be any data, including another array.
Wi
Tom
hopefully I’ve set this email not to hijack Harry’s thread.
First thing to note is that LC ONLY structures arrays as tVar[0][0][0]...
But equally we can use, for example, tVar[x][y][z] or tVar[x,y,z] or even
tVar[x,y,z][u,v,w][r,s,t]
However, know that, if x=1, y=“two”, z=true then tVar[x,y,
11 matches
Mail list logo
