Peter Brigham MD wrote:
On Feb 16, 2010, at 6:37 PM, Richard Gaskin wrote:
In my experience stack menus work perfectly UNLESS the height of the
stack being poppsed up is greater than the monitor height.
AFAIK Rev truncates stack rendering to the largest possible size,
which will be within
On Feb 17, 2010, at 1:05 AM, J. Landman Gay wrote:
Peter Brigham MD wrote:
Do you know *when* Rev does the truncation? I've had a problem with
certain printing stacks -- loaded up invisible or offscreen with
formatted text fields then printed with print card from x1,y1 to
x2,y2 into
Peter Brigham MD wrote:
head only mildly sore,
Good thing you are a doctor and can heal thyself. ;-)
Aloha from Hawaii,
Jim Bufalini
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and
On Feb 16, 2010, at 12:40 AM, Richard Gaskin wrote:
Peter Brigham MD wrote:
I'm already adjusting the height of the stack and placing the
menuItem groups appropriately, thanks. I was hoping to scroll the
whole stack. Putting everything into a group and scrolling the group
was what I was
On Tue, Feb 16, 2010 at 9:56 AM, Peter Brigham MD pmb...@gmail.com wrote:
Yes, I put this in the stack script and it works fine with the stack at
toplevel. What I may do is have a more... menuitem/button at the bottom of
the popup list when the list gets long, and use that to toplevel the
OK, now this is weird. All of a sudden, my stack menu is scrolling
automatically when I move the mouse down to the bottom. And if the
menu is short and I move the stack way down, the menu pops up above
the button to display fully instead of trying to appear below the
button where it would
Peter Brigham MD wrote:
OK, now this is weird. All of a sudden, my stack menu is scrolling
automatically when I move the mouse down to the bottom. And if the
menu is short and I move the stack way down, the menu pops up above
the button to display fully instead of trying to appear below
On Feb 16, 2010, at 6:37 PM, Richard Gaskin wrote:
In my experience stack menus work perfectly UNLESS the height of the
stack being poppsed up is greater than the monitor height.
AFAIK Rev truncates stack rendering to the largest possible size,
which will be within the monitor bounds.
Peter Brigham MD wrote:
Do you know *when* Rev does the truncation? I've had a problem with
certain printing stacks -- loaded up invisible or offscreen with
formatted text fields then printed with print card from x1,y1 to x2,y2
into pRect. I would show them to debug tweak the text
This is the first time I've really tried to use stack menus. I'm
building a stack menu during the course of user operations in a stack
-- it's a menu of recent images accessed, with thumbnails and stored
data associated with them. I've assigned a menustack as the menuName
of a pulldown
-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
Economy-x-Talk is always looking for new projects.
Op 15 feb 2010, om 20:14 heeft Peter Brigham MD het volgende geschreven:
This is the first time I've really tried to use stack menus. I'm
building a stack menu during the course of user
Peter Brigham MD wrote:
This is the first time I've really tried to use stack menus. I'm
building a stack menu during the course of user operations in a stack
-- it's a menu of recent images accessed, with thumbnails and stored
data associated with them. I've assigned a menustack as the menuName
Peter Brigham MD wrote:
Things are working fine, but a problem arises when the menustack gets
too tall. Clicking on the pulldown menu button pops up the menu, but the
bottom of it is chopped off, as it would descend below the screenrect. I
tried putting a rawkeydown handler in the menustack
Five votes from me.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig
On Feb 15, 2010, at 5:04 PM, Richard Gaskin wrote:
Peter Brigham MD wrote:
This is the first time I've really tried to use stack menus. I'm
building a stack menu during the course of user
I'm still wondering how a frontscript would work, as suggested by Mark
Schonewille. I hate to get into the complexities of a scrolling group
if I don't have to.
-- Peter
Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig
On Feb 15, 2010, at 6:04 PM, J. Landman Gay wrote:
Peter,
Actually, I assumed you would use a group with scrollbars. You will
also have to adjust the height of your stack by yourself, with a
preOpenStack script, and you'll need to set the height of the group to
the height of the stack.
--
Best regards,
Mark Schonewille
Economy-x-Talk
I'm already adjusting the height of the stack and placing the
menuItem groups appropriately, thanks. I was hoping to scroll the
whole stack. Putting everything into a group and scrolling the group
was what I was hoping to avoid. Sounds as if I'll have to, though, if
I want to proceed.
Peter Brigham MD wrote:
I'm already adjusting the height of the stack and placing the
menuItem groups appropriately, thanks. I was hoping to scroll the
whole stack. Putting everything into a group and scrolling the group
was what I was hoping to avoid.
Moreover, AFAIK it's not possible
Bill-
Monday, October 16, 2006, 6:50:59 PM, you wrote:
I'll try to make a feature request for the Menu Builder to offer not
to move things. I have a feeling that this trips up a number of folks
and it looks like Rev knows how to prevent the problem.
My workaround for this is never to use
Hi Bill,
Your requested feature already exists. When you make a new menubar, a
window appears to choose a stack and give the new group a name, with
a checkbox giving you an option to move objects down to accommodate
for the menu bar.
Best regards,
Mark
--
Economy-x-Talk
Consultancy
We've been warned that there are problems with menus on multiple
cards, however I have successfully and easily added menus to a single
card stack, where background groups are switched in and out of
visibility with no problems, and the data is provided by a database.
Does using multiple cards
Mark Wieder wrote:
Bill-
Monday, October 16, 2006, 6:50:59 PM, you wrote:
I'll try to make a feature request for the Menu Builder to offer not
to move things. I have a feeling that this trips up a number of folks
and it looks like Rev knows how to prevent the problem.
My workaround for this
I think I missed the feature when I created it. What I needed was the
reverse which would have been NOT to move everything back up.
Bill
On Oct 17, 2006, at 3:15 AM, Mark Schonewille wrote:
Hi Bill,
Your requested feature already exists. When you make a new menubar,
a window appears to
I have been happily developing a stack with menus. To make life simpler
with the IDE I didn't have them Set as menubar on Mac OS in the Menu
Builder dialog box. This put the stack menus on the screen but left the
IDE menus available for me to use and has worked great up to now.
I'm about
Bill Vlahos wrote:
I'm about finished with the stack so I checked the box then all hell
broke loose.
1. Everything shifted up when the menus were removed. I sort of expected
this and thought that I could simply move everything down appropriately
and get on with life. (BTW it would be nice
Bill,
One trick I've learned that keeps the other controls from shifting up
is to hide your menu group first, and then set as menubar on Mac OS.
Of course, if this app has to run on Windows as well, you'll have to
show the menu group via your code if the platform is Win32.
Otherwise, no
Thanks to Jacqueline and Chris. They both gave me clues.
What I did to fix it was simply delete the menu group entirely. When
you do that Rev asks if you want to move everything back up and
delete the objects. I said no and it didn't move anything but it did
delete the menus. I don't know
27 matches
Mail list logo
