 |
Caled Sorcerer
Joined: 21 Oct 2000 Posts: 821 Location: Australia
|
Posted: Thu Feb 26, 2009 8:29 am
[3.03] Suggestion: "File > View package" |
I think if I open a package with this command instead of the standard "File>Open.." that the package ought to be set to local only.
|
|
_________________ Athlon 64 3200+
Win XP Pro x64 |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Feb 26, 2009 5:24 pm |
I'm not sure what you mean by "local only". Do mean "read only"?
|
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Thu Feb 26, 2009 6:20 pm |
I think he perhaps means that modules inside the viewed package should be set to local rather than global or external modes. Because you're viewing rather than opening the package (to look at what it contains, rather than to run it and use it) it should be prevented from interacting with the scripts and windows already present in the session.
|
|
|
 |
Caled Sorcerer
Joined: 21 Oct 2000 Posts: 821 Location: Australia
|
Posted: Fri Feb 27, 2009 7:22 am |
Yeah, that's exactly what I meant. I opened one to view (to search my old curing package for trigger lines my new one might be missing) and somehow it caused a fairly nasty loop (it still doesn't make sense -how- actually, hehe). It occurred to me that the point of having "view" as distinct from "load" is probably so I can look at an unknown package safely.
For example, if I got a package from someone else and want to make sure its not malicious. (A lot of packages are shared by email and not the library still, because people often don't want to share a package to everyone.) |
|
_________________ Athlon 64 3200+
Win XP Pro x64 |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Fri Feb 27, 2009 5:47 pm |
I understand now. That's a bit tricky to implement but I'll add it to the to-do list for the future.
|
|
|
 |
|
|