Hi Jan,
Yes, this was what I originally expected. But it's not working as of yet
during runtime... only in the development environment. Will this be
implemented shortly (prior to launch) so that it works the same during
runtime? What if the two stacks are sized differently? What will happen
then?
It would be nice to have answers to these now so that developers like
myself can make adjustments based on fairly large items like this.
I've discovered some other significant (for me) change to the runtime
environment in the past few days. A traditional cascading menu (built
with the menu builder).... which worked fine yesterday during runtime...
no longer works today. The menu (which I dragged to the center of the
stack so it functions as a button with cascading selections), depresses
OK. The list of hierarchical selections show up OK. But any attempt to
actually make a selection fails.
Obviously, they are making substantial changes to the runtime
environment on a daily basis. This makes development very difficult. I
can work around much of this and focus on other items, but it's the "not
knowing what we'll end up with by 11/11" that makes all of this
stressful, if not impossible. I actually don't think they know either.
It seems to be very much a day-by-day situation. On the other hand, I
fully appreciate the enormity of the challenge they face.
Richard
Jan Schenkel wrote:
--- On Thu, 10/29/09, Richard Miller <[email protected]> wrote:
Richard (or anyone else),
In the "known issues" section
(http://revmedia.runrev.com/frequently-asked-questions/known-issues/)
covering Revmedia, it is stated that "go in window of stack"
will be fixed shortly. What do you interpret this
functionality to mean? It obviously doesn't relate to "go to
card x", since that works fine now.
Thanks.
Richard Miller
Hi Richard,
Using 'go stack "OtherStack" in the window of this stack" you can go to another
stack without leaving the current window - it's as if the target stack window opens in the
same rectangle as the original stack and then the original stack window closes, but without
the actual opening and closing of windows.
Just give it a try:
- create a new stack "MyMain"
- drop in a button "Go sub" with script
on mouseUp
go stack "MySub" in the window of this stack
end mouseUp
- create a new substack "MySub"
- drop in a button "Go main" with script
on mouseUp
go stack "MyMain" in the window of this stack
end mouseUp
Now play around with it, and you'll see that the same window remains open and
you're just hopping back and forth seamlessly between the mainstack and
substack.
To me, this sounds like the best interim solution for revlets' inability to
open new windows for substacks - and it certainly fits in with the AJAX
paradigm of modifying the current page rather than loading a whole new page.
Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>
=====
"As we grow older, we grow both wiser and more foolish at the same time." (La
Rochefoucauld)
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
