Multiple Screen Issue

[sturgis]

Notice the hiliting in the script editor for your case statements

This: case "revLoadedStacks("All")"

Is actually: case "revloadedstacks(" followed by the keyword All, followed by ")" rather than checking against a full string including quotes.

Either change your button label to a simpler form (I'm lazy its what i'd do) such as "revloadedstacks (all)" without the integrated quotes, and set your case statement to match, or....

Alternatively, you can build up the string, or use a merge.

case merge("revLoadedstacks([[quote]]All[[quote]])") -- merge method. merges the quotes in

case ("revLoadedStacks(" & quote & "Application" & quote & ")") -- build up the string

[BarrySumpter]

LOL. Jeez! Thats embarrasing!

Thanks heaps.
Its gettin late n I'm gettin ditsie.

[sturgis]

Hey, was just thinking (always a bad thing) I don't use "do" much, so its not the first thing that occurs to me, but..

If you comment out the whole switch/case segment, and change your labels slightly you can replace it with this:

Code: Select all

  do "put" &&  tStacks && "into tWindows"

So, your labels would have to change to:

the Stacks
the OpenStacks
the mainStacks
revLoadedStacks("All")
revLoadedStacks("Application")

I doubt there will be any noticable change in execution speed, but doing it this way you can pretty much incorporate any string as a label on your button that do can evaluate without having to mess with more case statements. That way it should work for things like the screenrects, or.. well, pretty much anything that can be evaluated by do.

Of course you would still have to handle varying styles of returned data, but even so, might be pretty slick.

Also, I noticed one other thing. "the stacks" returns a blank line for any open stack that hasn't been saved yet, so right after your switch block where you have your repleat loop, might put a check for empty in there to avoid an error. (can't get the rect of a blank stack name)

[BarrySumpter]

OK, I'll ask again.
Where do you guys get this stuff?
Is there a reference I don't know about?

I can do this:
edit the script of button btnDummy

but not this:
close the script of button btnDummy

[sturgis]

OK, I'll ask again.
Where do you guys get this stuff?
Is there a reference I don't know about?

I for one dig through every bit of other peoples code that I can find. (that message watcher is a real gem!) I'm also a dictionary browser (and I always look through the "also see" section of a listing if there is one), a lessons.runrev.com checker, and was on the mailing lists for a while. (lots of cool stuff there, and the archive is searchable.)
Need an example that uses sockets for client server communication? Look at chatrev. Want an example of a basic rev-built webserver? Soapdog can hook you up. Need help dealing with date/time functions, quirks, date pickers.. Sarah Reichelt is da Man!.. well you know what I mean.

While the documentation, tutorials, and general resources have improved, and are still improving, my belief is that livecode's greatest strength is all the helpful people. (on both the end user side, and the dev side)

I can do this:
edit the script of button btnDummy

but not this:
close the script of button btnDummy

Haven't dealt with the script editor stuff much, so managing that would better be in someone elses bailiwick. Of course, since the script editor is made from rev, you can always dig through it to see if there is anything useful. Probably easiest method would be to clone stack "newScriptEditor 1", rename the new stack to something safe and non-rev prefixed then explore it to your hearts content.

Just my 2c.

[BarrySumpter]

More like $200 worth.

Code: Select all

do "put" &&  tStacks && "into tWindows"

There you go again! LOL
Couldn't get just the put to work.
So was more interested in seeing the results so just dropped it n hard coded it.
Thanks again.


I was really asking about where you got all the LC IDE stuff.
But certainly acknowledge theres more out there than I could ever chase down.
I'm sure I need to do a reality check and acknowledge I've only been at this for 6-7 months.

Just found out about the topLevel.
I was deducing that the stacks were locked in some way to be researched later
like the scratched metal background stack
so I've got heaps of stacks to review to see if I can crack them open.

I really need to get my version of the Bvg Doco 2 sorted out
so I can start adding heaps of references and scripting examples.

I've been seeing more mailing list posts search results over the last couple of weeks.
I haven't had the chance to chase down how to join the multitude of mailing lists as yet.
Or where to go to limit my search for a specific mailing list.

So used to IDEs being locked away
I hadn't had the chance to put 2 n 2 together
to get Toplevel n Script Editor to look thru its code.

There's only so much research n testing you can do before you have to have a fair go at a real project and start really stumbling your way thru.

[BarrySumpter]

Code: Select all

... that livecode's greatest strength is all the helpful people ... 

Yes, and so many of them throughout the last decade.

Sorted all kinds of issues with this last BGS4 version.
Thanks heaps for all your help and suggestions.

I've included a snap of my most efficient layout for a single screen.

When bgs4 stack height expands to show the various stacks lists,
you can just click on the bgs4 card background to reduced the height again.

----

next I wnat to have a quick look at idShowSreen
and see if I can add an export to file and an import from file
to save the current layout settings - save file as - and let you name the file
and retrieve saved layout settings and arrange stacks by applying those retrived settins.

[WaltBrown]

Barry wrote:

Anyone know how to save all these positions?
I can move them around but on LC close then LC open all the stacks are in differnt places than when I left them.

Some of the rev stacks have a custom property called "cREVRestoreLoc". I haven't messed with it too much. I have tried adding it to stacks which do not already have it, but it has no effect - there is no general engine operation which looks for it, it's stack dependent. I assume LC uses that when it opens Rev stacks to set their location, which I think is why yours aren't remembered.

I made a slightly newer version, which opens up all the rev stacks and their substacks - it's a lot of fun if not all that useful to see all the stacks. It may be interesting to those who map a lot of stacks or substacks off screen.

[ARRRGH]
Just opened it, it's the old version, I neglected to save again.
[/ARRRGH]

[mwieder]

In general it's not a good idea to mess around too much with the "cREV..." custom properties - they're used by the IDE and not by the engine. Adding a cREV... custom property to a stack that doesn't already have it may or may not do anything for you. If something in the IDE uses it or relies on it then you may or may not mess things up.

That said, it's sometimes quite instructive to experiment with the cREV custom props and watch how they change and what happens when you modify them. Save backup copies of everything..

[mwieder]

I for one dig through every bit of other peoples code that I can find.

I find that absolutely the best way to learn. The dictionary is useful, the online samples are useful, but seeing how other people have tackled problems is the way I absorb things best.

That and drawing on the collective wisdom and experience of the community. Chances are good that somebody's already gone down the path that has me stumped or made the same mistakes that I'm currently making.

[mwieder]

Barry- that layout looks quite nice. It's starting to approach an Eclipse-style view of things. I have the silly menubar icons turned off for a more compact view, but otherwise I quite like it.