Stacks!?! why do you use them?

1235»

Comments

  • Reply 81 of 83
    dfilerdfiler Posts: 3,420member
    Maybe I should have brought up that stack-items-are-objects a bit earlier. It does a lot to explain why additional programming was needed instead of just rehashing the old menu-handling code.



    With stack items being objects (file system objects even), there are a whole slew of behaviors to support in order to remain consistent with other objects in the GUI and file system.
     0Likes 0Dislikes 0Informatives
  • Reply 82 of 83
    pbpb Posts: 4,255member
    Quote:
    Originally Posted by dfiler View Post


    Exactly. Stacks have options and types of interaction than aren't found in menus. All this functionality had to be programmed and tested. It wasn't simply reuse of existing code.



    OK, I did not know that. This indeed makes programming much more complex.



    Quote:
    Originally Posted by dfiler View Post


    But with that said... who knows. The initial lack of list-view could have been an intentional design decision rather than an a missed implementation or testing deadline.



    In the light of the previous clarifications, indeed, we cannot know for sure what happened.
     0Likes 0Dislikes 0Informatives
  • Reply 83 of 83
    Quote:
    Originally Posted by dfiler View Post


    Maybe I should have brought up that stack-items-are-objects a bit earlier. It does a lot to explain why additional programming was needed instead of just rehashing the old menu-handling code.



    Indeed it's a whole new way of working, however I'm guessing that in order to bring up a contextual menu, it would be a case of simply invoking a "verb menu" instead of a "stack object".



    The only thing I'm really bothered about though is being able to turn off the nice-but-confusing stack icons.
     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.