[AccessD] Wish List.

The way we handled the X button issue in VB.Net was to have a
close/back/exit button (with caption) in a standard location at the bottom
of all forms, along with a menu item at the top to call the same routine.
The rule of thumb was to always give the user multiple ways of getting
there.

Charlotte Foust

On Thu, Sep 8, 2011 at 4:48 PM, Darryl Collins <
darryl at whittleconsulting.com.au> wrote:

> Aaah, thanks everyone for their thoughts and comments. It is entirely
> possible that I am just doing this the hard way (wouldn't be the first
> time).   Anyway, I will probably end up using tabs like always.
>
> I don't like the way you have to leave the label visible at the top of the
> page though - even if only one tab is displayed. Visually it is not what I
> want, but I guess its all I have to work with.
>
> Anyway, didn't mean to get folks fired up about what is a tab or what is a
> page.  Sometimes I think it would be nice if you could take the best of all
> the software UI and include it in a single package.
>
> Ok: Here is another prime example of poor user functionality - or more like
> sheer bloody laziness on behalf of MSoft.  If I am using Firefox tabs in
> the
> browser, right on the *Active* tab there is a little "X" on the RHS of that
> tab that allows you to close it. Nice and useful, don't have to move the
> mouse far and it is darn clear which tab you are going to close.
>
> In A2007 (which uses a tab setup to display all the open DB objects such as
> forms, tables, queries etc) the close button is on the extreme RHS of the
> *Screen* - freakin miles away from where you are actually working.  Now I
> have huge widescreen monitor at work and if I have single tab open there is
> about 1 foot (say 28 cms) of screen real estate between the active tab I am
> working on, and the little 'close tab' "x" on the RHS of the screen.  Even
> more annoying is if you have many tabs open, you need to double check the
> one want to close is indeed the active tab before pressing the "x"
>
>  - ok there are other ways of closing the tab, such as right mouse click
> directly on the tab, but why on earth didn't they just put the close "X" on
> the active tab like everyone else does.
>
> Little gripes, I wouldn't mind so much if I didn't have to pay MS so darn
> much for their software.  I don't mind paying, but I expect better
> functionality and performance than I can get for free from other vendors.
>
> Heh, can you tell I need a coffee ;)
>
> Cheers
> Darryl.
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
> Sent: Friday, 9 September 2011 6:48 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Wish List.
>
> I'm not sure which version the multipage control was introduced in
> (probably
> 2007), but it serves the same purpose as the tab control was introduced for
> back in A95 or A97.  Tab controls actually do have pages, which you insert
> much the same way, although they aren't very intuitive either.  I don't
> know
> why they came up with another control to do the same thing, but such is the
> world of Microsoft.
>
> Charlotte Foust
>
> On Thu, Sep 8, 2011 at 12:18 PM, Mark Simms <marksimms at verizon.net> wrote:
>
> > Once again I think confusion abounds:
> > Multipage has tabs with associated pages to allow insertion of other
> > controls, etc.
> > The Tab Control is just this tiny thing that has tabs with no pages.
> >
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
>
>
> Website: http://www.databaseadvisors.com
>
>
>