I repeatedly find myself in positions where I attempt to pick up a stack of cards in proper order, but am unable to do so (only the card I clicked appears, and the stack cannot be moved).
This most commonly happens when the shuffle coincidentally lays the cards in proper stacking order, but also seems to occur when I move a stack onto a card, and then try to lift the "new" stack to another place.
Am I missing something?
I repeatedly find myself in positions where I attempt to pick up a stack of cards in proper order, but am unable to do so (only the card I clicked appears, and the stack cannot be moved).
This most commonly happens when the shuffle coincidentally lays the cards in proper stacking order, but also seems to occur when I move a stack onto a card, and then try to lift the "new" stack to another place.
Am I missing something?
AFAIK you can¥t really move stacks, just single cards. Only if there are enough free cells to hold the stack minus one card you may move a stack.
Georg ---- Dipl.Ing. Georg Gollmann TU-Wien, Zentraler Informatikdienst Wiedner Hauptstr. 8-10 phon:(+43-1) 58801 - 42022 A-1040 Wien fax: (+43-1) 58801 - 42099 mail:gollmann@zid.tuwien.ac.at http://macos.tuwien.ac.at/Gollmann.html
I repeatedly find myself in positions where I attempt to pick up a stack of cards in proper order, but am unable to do so (only the card I clicked appears, and the stack cannot be moved).
This most commonly happens when the shuffle coincidentally lays the cards in proper stacking order, but also seems to occur when I move a stack onto a card, and then try to lift the "new" stack to another place.
Am I missing something?
AFAIK you can¥t really move stacks, just single cards. Only if there are enough free cells to hold the stack minus one card you may move a stack.
Yes. I put in the stack hack. Georg is correct -- you can only move single cards by the game def. But you frequently discover that with N cells free and M stacks open, you can move stacks of a certain size (Think of it as a macro ;-). I figured out the limit once (something like N*(2^M)), but (a) I don't know if I got it right, and (b) if the destination is one of the open stacks, then the numbe is reduced, and I may not have handled that right (though I tried) The idea was: Let the user pick up stacks up to the max size that could be moved and, if he drops it in an open stack such that it would not have been possible, abort the move upon the drop. [Some other FreeCell programs know both source and dest when they start the move so it is simpler: the move either happens or it doesn't].
- Dan
I'm using SubMenus with stayUp items, and I'm having 3 problems. None are major, but they are annoying. I was wondering if anyone has done anything like this before I dig into the code much more.
1. When you select 'keep this menu up' the submenu goes away when you release the mouse. When you reclick the parent menu item, the submenu reappears, with stayUp = true. I'd like the behavior to be like the top level menus, where it stays up right away.
2. When you dismiss a menu if it has an open subMenu the subMenu stays up. Clicking dismiss on the submenu then raises an MessageNotUnderstood error. How can you find open submenus to dismiss? I looked around in explorer and couldn't find any obvious flags like open = true or display = true.
3. Mouse droppings. The only place I consistently get mouse droppings in Squeak is when I use submenus. The rightmost (or leftmost, depending on placement) line sometimes remains at 1 pixel width. I assume there is a BilBlt method for redrawing after a menu goes away that should get widened by 1 pixel, but I haven't dug into it.
Any help with any itmes would be greatly appreciated.
-Russell Swan
squeak-dev@lists.squeakfoundation.org