XYplorer Beta Club

How about add an option to wrap the buttons toolbar into extra rows when there are too many buttons, instead of cropping them? Similar to how the menu wraps. This is useful for seeing all buttons, even when working in a reduced size window mode.

I'm all for it since currently adding buttons to the toolbar leads to invisible buttons - existing buttons are just pushed out of the visible field while other are added, rendering them inaccessible.
Ideal solution:

I think this functionality would compliment introduction of "unlimited" number of CTBs. This is because currently there are only so many buttons one can put on TB. In addition, stretching the TB with lots of buttons horizontally doesn't look good if a user is in SP mode with a handful of columns, it creates too much "white space" on the right side of the program window.

SkyFrontier wrote:

Code: Select all

Ideal solution:

[button 1][button 4][button 5][button 6]>>|i|
                                        [button 2]
                                        [button 3]
(>>) being the button to show extra buttons on toolbar.

that approach might be good for preserving screen space. but i would still prefer it to expand into multiple rows so the buttons can still be accessed via 1-click. perhaps makes either of these an option?

TsunamiZ wrote:that approach might be good for preserving screen space. but i would still prefer it to expand into multiple rows so the buttons can still be accessed via 1-click. perhaps makes either of these an option?

Also, please consider how having multiple TB button rows can impact application layout and handling of a layout's components This is particularly pertinent to situations with multiple items in one layout style

SkyFrontier wrote:Ideal solution:

Code: Select all

[button 1][button 4][button 5][button 6]>>|i|
                                        [button 2]
                                        [button 3]
(>>) being the button to show extra buttons on toolbar.

I think this is also the most common solution. I have it on my list since a while. Patience...

We must have in mind that icon sizes now are changeable, so if one badly needs extra space for additional icons there's only the option to "Tools\Customize Toolbar (CTRL+SHIFT+F9)\untick 'Large Icons'".
Also, there were some user reports on successfully adding 100 icons to each right/left mouse click, which grants us a handful of space to work with. When I realized the power of CTB I was astonished, but took a time to comfortably handle the method for adding scripts/"buttons".

Also for the records, keep in mind that the method to add parameters is:
As I see in v7.30.0027 - 2008-07-26 21:46,
I assumed that above possibilities would also apply to CTBs. They don't. At least when "importing" parameters from a shortcut - must have something with using "/" instead of "-". Have to run a second battery of tests later. lol

admin wrote:

SkyFrontier wrote:Ideal solution:

Code: Select all

[button 1][button 4][button 5][button 6]>>|i|
                                        [button 2]
                                        [button 3]
(>>) being the button to show extra buttons on toolbar.

I think this is also the most common solution. I have it on my list since a while. Patience...

I'm just working on this. Does anybody know how this feature is called? ([button 2] and [button 3] etc. will be shown in a menu popped by pressing ">>"). Every standard toolbar has this but I cannot find the name for it...

admin wrote:I'm just working on this. Does anybody know how this feature is called? ([button 2] and [button 3] etc. will be shown in a menu popped by pressing ">>"). Every standard toolbar has this but I cannot find the name for it...

It's "overflow".. but I'm not finding much about it for VB outside of .NET.

http://msdn.microsoft.com/en-us/library/ms234871.aspx almost makes it sound like overflow isn't possible in 6.0...

Wrappable Property

In Visual Basic 6.0, the Wrappable property of a ToolBar control determines whether the toolbar buttons will automatically wrap when the window is resized.

The Visual Basic 2008 ToolStrip control has no direct equivalent; it supports the use of a dropdown overflow menu instead. When you add ToolStripItem elements that require more space than is allotted to the ToolStrip, given the form's current size, a ToolStripOverflowButton automatically appears on the ToolStrip. The ToolStripOverflowButton appears, and overflow-enabled items are moved into the drop-down overflow menu. You can disable this behavior by setting the CanOverflow property to False.

TheQwerty wrote:

admin wrote:I'm just working on this. Does anybody know how this feature is called? ([button 2] and [button 3] etc. will be shown in a menu popped by pressing ">>"). Every standard toolbar has this but I cannot find the name for it...

It's "overflow".. but I'm not finding much about it for VB outside of .NET.

http://msdn.microsoft.com/en-us/library/ms234871.aspx almost makes it sound like overflow isn't possible in 6.0...

Wrappable Property

In Visual Basic 6.0, the Wrappable property of a ToolBar control determines whether the toolbar buttons will automatically wrap when the window is resized.

The Visual Basic 2008 ToolStrip control has no direct equivalent; it supports the use of a dropdown overflow menu instead. When you add ToolStripItem elements that require more space than is allotted to the ToolStrip, given the form's current size, a ToolStripOverflowButton automatically appears on the ToolStrip. The ToolStripOverflowButton appears, and overflow-enabled items are moved into the drop-down overflow menu. You can disable this behavior by setting the CanOverflow property to False.

Thanks!

(Of course, I don't care what's "possible" in Visual Basic 6.0 -- XY does not use VB 6 controls appart from buttons. )

zer0 wrote:Also, please consider how having multiple TB button rows can impact application layout and handling of a layout's components This is particularly pertinent to situations with multiple items in one layout style

I like the multiple TB rows better than wrapping. I can put all my often used ones on one row, and less used ones in a second row. That allows us to easily turn on/off individual rows, which would be especially useful when working with small screen space. This way we can have any layout we want. If XY wraps its for us, it will not be nearly as useful, IMO. Also, maybe turning rows on and off might be easier coding than wrapping.

scrollable tooblar is better than nothing. but i also prefer having it wrap into multiple rows because it would allow instant access to buttons instead of having to scroll. would be nice to have options.