Codejock Developer Community : Add or Remove Buttons vs Customize Dialog

Add or Remove Buttons vs Customize Dialog : There is nothing to fix, you just...

Fri, 24 Feb 2006 08:27:24 +0000

Author: Oleg
Subject: 3527
Posted: 24 February 2006 at 8:27am

There is nothing to fix, you just don't understand basic idea.

Reset button do the thing that it must do - Revert all changes was done after last EnableCustomization call.

See this sample and make same in your application.

2006-02-24_082152_ds.zip

Add or Remove Buttons vs Customize Dialog : oleg wrote:Replace it to C...

Thu, 23 Feb 2006 18:27:43 +0000

Author: dajv
Subject: 3527
Posted: 23 February 2006 at 6:27pm

oleg wrote:

Replace it to

CommandBars.LoadDesignerBarsCommandBars.FindControl(, ID_FILE_PROPERTIES, , True).Visible = FalseCommandBars.EnableCustomization True CommandBars.LoadCommandBars "Codejock Software ActiveX Demos", App.Title, "Layout"

to fix it.

Your fix is something I had considered (if you read the previous posts I have made in this thread). What it means is that whenever the visible state of a control needs to be changed, I need to call EnableCustomisation. As I said here:

dajv wrote:

As I would expect is pretty standard among many applications, certain buttons are hidden from the user depending on the context they are in. These hidden controls SHOULD NOT appear in either the toolbar submenu of the "Add or Remove Buttons" menu or when the customize dialog is shown.

The visible state of controls change depending on the context a user is in.

Lets take Outlook as an example of this.
1) Go to Inbox. Assuming you haven't customised the toolbar, the following toolbar will be shown:

2) Go to Calendar. Assuming you haven't customised the toolbar, the following toolbar will be shown:

This is a pretty standard way for an application to behave. CodeJock needs to support this behaviour. (Edit: What I mean by support, is that when you Reset the toolbar in Outlook, it does NOT show the menu items from Calendar if you are in Mail, for example. With the CodeJock CommandBars, this DOES happen, as I showed in previous screenshots.)

The thing to notice here is that the toolbars are different based on the context. One is in Mail, the other is in Calendar. The user can go back and forth between these. This means the visible state of the controls needs to change. Using your fix, this means calling EnableCustomization after every change. This means that whenever the user "resets" their toolbar, the point it will be reset back to will be the last time the visible state of a control changed. Since this is going to be often, the reset becomes useless.

All this is a reiteration of things I have already said in previous posts in this thread.

I feel we are going around in circles here. This is something that really needs to be fixed, and I can imagine we are not the only ones who suffer from this - if others were to test their this part of their application they would see this is how the CodeJock control behaves.

We are getting close to release and we cannot release our software with this bug. Here is what I propose:

You provide a setting to hide the "Reset" button on the customise toolbar menu. This means that the only way a user can reset is by using the Customize dialog.

Remember that the problem we are talking about here is caused by being able to reset the toolbar from this menu. See my previous posts for more information about this.

Add or Remove Buttons vs Customize Dialog : Replace it to CommandBars.Lo...

Thu, 23 Feb 2006 07:57:10 +0000

Author: Oleg
Subject: 3527
Posted: 23 February 2006 at 7:57am

Replace it to

CommandBars.LoadDesignerBars
CommandBars.FindControl(, ID_FILE_PROPERTIES, , True).Visible = False
CommandBars.EnableCustomization True

CommandBars.LoadCommandBars "Codejock Software ActiveX Demos", App.Title, "Layout"

to fix it.

Add or Remove Buttons vs Customize Dialog : Can I please get an answer to...

Tue, 21 Feb 2006 18:50:39 +0000

Author: dajv
Subject: 3527
Posted: 21 February 2006 at 6:50pm

Can I please get an answer to the below? There is no way for me to work around the problem, and it really does need to be fixed before we release our software.

dajv wrote:

oleg wrote:

You write a lot, but I don't understand your problem.

I like to make sure I describe it as fully as I can otherwise I get a different answer to a different question. Its better for me to include more information than less.

oleg wrote:

Simply point -

- You _must_ call EnableCustomization only once after you create toolbars.

OK.

oleg wrote:

- Buttons with Visible = False not appear in ""Add or Remove Buttons" menu"

There is problem?

Yes, they do appear in the "Add or Remove Buttons" menu after clicking "Reset". This can be seen in the CommandBars "Designer Sample I have modified and attached.

Here is a picture, also:

2006-01-19_003424_DesignerSample.zip

Add or Remove Buttons vs Customize Dialog : SuperMario wrote:Actually,...

Mon, 23 Jan 2006 18:00:04 +0000

Author: dajv
Subject: 3527
Posted: 23 January 2006 at 6:00pm

SuperMario wrote:

Actually, ShowExpandButtonAlways always hides the dropdown button.� This will not stop users from accessing button when the window is too small...a different type of button is shown then.� This will not stop users from accessing buttons that were visible when the window was expanded.

Well we're just playing with words now. It doesn't appear to be a different button to me, at all.

I'm just repeating what we already know here, but when ShowExpandButtonAlways is True, the expand button is shown always. When there is not enough room to show all the controls, the expand button is also shown. The only difference is that it now also shows controls that can't fit in the window.

ShowExpandButtonAlways = False simply stops the expand button from being shown when there is enough room to show all the controls. When there isn't enough room, the expand button is present.

There needs to be a way of hiding the Add or Remove Buttons menu if the problem I have outlined above cannot be addressed.

Add or Remove Buttons vs Customize Dialog : Actually, ShowExpandButtonAlways...

Mon, 23 Jan 2006 07:23:43 +0000

Author: SuperMario
Subject: 3527
Posted: 23 January 2006 at 7:23am

Actually, ShowExpandButtonAlways always hides the dropdown button. This will not stop users from accessing button when the window is too small...a different type of button is shown then. This will not stop users from accessing buttons that were visible when the window was expanded.

Add or Remove Buttons vs Customize Dialog : Also, regarding hiding the Add...

Sun, 22 Jan 2006 18:40:04 +0000

Author: dajv
Subject: 3527
Posted: 22 January 2006 at 6:40pm

Also, regarding hiding the Add Or Remove Buttons menu, in this thread,
https://forum.codejock.com/forum_posts.asp?TID=2686&KW=expan d
someone asks how to hide the "expand button" so as to hide the Add or Remove Buttons menu. As the property name suggests, ShowExpandButtonAlways only applies when the commandbar does not fit in the window. In this case, setting ShowExpandButtonAlways to false will only hide it when there is enough room to show the commandbar. Otherwise the user can still access the Add Or Remove Buttons menu.

Is there a way to hide the Add or Remove Buttons menu all the time, without stopping the user from accessing controls on the commandbar that can't be shown because there isn't enough room?

This would be a last resort if the problem outlined in the above posts can't be fixed.

Add or Remove Buttons vs Customize Dialog : Please let me know if you're...

Sun, 22 Jan 2006 15:41:50 +0000

Author: dajv
Subject: 3527
Posted: 22 January 2006 at 3:41pm

Please let me know if you're looking at this or if I need to make it any clearer.

Add or Remove Buttons vs Customize Dialog : oleg wrote:You write a lot,...

Thu, 19 Jan 2006 00:34:31 +0000

Author: dajv
Subject: 3527
Posted: 19 January 2006 at 12:34am

oleg wrote:

You write a lot, but I don't understand your problem.

I like to make sure I describe it as fully as I can otherwise I get a different answer to a different question. Its better for me to include more information than less.

oleg wrote:

Simply point -

- You _must_ call EnableCustomization only once after you create toolbars.

OK.

oleg wrote:

- Buttons with Visible = False not appear in ""Add or Remove Buttons" menu"

There is problem?

Add or Remove Buttons vs Customize Dialog : You write a lot, but I don'tunderstand...

Thu, 19 Jan 2006 00:09:34 +0000

Author: Oleg
Subject: 3527
Posted: 19 January 2006 at 12:09am

You write a lot, but I don't understand your problem.

Simply point -

- You _must_ call EnableCustomization only once after you create toolbars.

- Buttons with Visible = False not appear in ""Add or Remove Buttons" menu"

There is problem?