Hi, Tim,

Yes, I've considered that, but, as of yet, I've been unable to come up with a 
meaningful graphic.  Also, I know the default graphic is being used in other 
modules, so to change the default to something else for usage in my own module 
would make it even more confusing for users of multiple modules who are 
acustomed to knowing that that particular icon means what it does.

In addition, in the button caption, I like to put the function (such as F8, 
etc.) that triggers the button's action.

Thanks for the suggestion.

Kevin


  ----- Original Message ----- 
  From: Tim McCaron 
  To: [email protected] 
  Sent: Sunday, December 03, 2006 7:35 PM
  Subject: RE: [vassalengine] Enhancement Requests


  Oops hit sent before I typed a reply.

  Kevin - in regards to number one, have you considered replacing the default
  icon with something graphically more clear? A symbol with text in it? I
  usually always replasce the default icons so they are obvious to their
  intent. Likewise, for you, you may find doing so would make the point of
  need for text over pop ups mute in the meantime till this changes.

  _____ 

  From: [email protected] [mailto:[EMAIL PROTECTED] On
  Behalf Of Kevin Coombs
  Sent: Sunday, December 03, 2006 5:18 PM
  To: [email protected]
  Subject: Re: [vassalengine] Enhancement Requests

  Hi, Brent,
  Responses below.
  Kevin

  ----- Original Message ----- 
  From: Brent Easton 
  To: vassalengine@ <mailto:vassalengine%40yahoogroups.com> yahoogroups.com 
  Sent: Sunday, December 03, 2006 3:23 PM
  Subject: Re: [vassalengine] Enhancement Requests

  Hi Kevin,

  >1) Presently, text can be added to the "Zoom In," "Zoom 
  >Out," "Show/Hide Pieces" and "Image Capture" buttons. Can text be 
  >added to the "Mark all pieces on this map as not moved" button 
  >currently? If not, could this be added as an enhancement?

  Is this so that you can add the 'Mark All Pieces' button to a
  toolbar menu?

  No, this is for usability only. I like to put captions on all the buttons so
  there is no mistaking what they are for. I even caption the Zoom In and Zoom
  Out buttons so that the novice or newbie user knows what these buttons are
  for. The Mark All Pieces Unmoved button is even more obscure and, therefore,
  I feel even more in need of a caption. This is why the request.

  >2) The Line of Sight Thread feature offers the ability to set the 
  >opacity level of hidden pieces to a certain percentage. Could this 
  >ability to set opacity level be added to the "Invisible" property?

  How do you want to use this? There is already a RFE for an 'Opacity'
  trait that can have a variable Opacity level based on a Dynamic
  Property. Would that achieve what you want?

  Yes, that RFE might do what I'm trying to achieve. Thanks.

  >3) Currently, is there any way to add a menu option to the window 
  >menu area (where the "File" and "Help" menu items reside), either 
  >within the "File" menu option itself, or as a new menu option 
  >alongside the "File" and "Help" menu options (with other sub-menu 
  >options within it)? If not, could this ability to add menu options 
  >to the window possibly be added as an enhancement?

  Basically the same as a Toolbar menu, but create a drop-down menu in
  the main menu bar instead of a button in the toolbar?

  Umm, not really a drop-down menu. I'm just thinking another menu option in
  the lines of the "File" and "Help" menu options that already exist. For
  example, when my module opened, there would be the standard "File" and
  "Help" menu options, but I could have another menu option there as well,
  such as "Actions." When the "Actions" menu option was selected, a list of
  other menu options would then be visible to choose from (similar to
  selecting "File" menu option then "Save" menu option). Again, this is
  strictly for usability. My real reason for requesting this is because I have
  an item or two that will only be used once per game (if ever). Creating
  buttons for these seldomly used items takes up too much real estate. A
  better solution would be to create these items as menu options so that they
  are out of the way and only visible when (and if) needed.

  Regards,
  Brent.
  __________________________________________________________
  Brent Easton 
  Analyst/Programmer 
  University of Western Sydney 
  Email: [EMAIL PROTECTED] <mailto:b.easton%40uws.edu.au> edu.au

  [Non-text portions of this message have been removed]

  [Non-text portions of this message have been removed]



   

[Non-text portions of this message have been removed]

Reply via email to