XYplorer Beta Club

My view is "[Toolbar & Address Bar]".

With 8.90 the toolbar now scrolls/drops down when its width exceeds the available width and the Address Bar does not resize.

I believe that prior to 8.90 the Address Bar reduces in size in order to accommodate the width of the toolbar, which is behaviour I personally prefer (because all the toolbar buttons are visible AND the Address Bar is still available, albeit reduced in size).

Would it be possible to make the new scrolling/dropping down of overflow toolbar buttons optional, so that I can have the previous behaviour if I prefer?

I'm sure the new behaviour will be welcomed by many but for one at least (i.e. me) this is the first 'improvement' where I actually preferred the previous implementation! (Sorry!)

Thanks!

Pete

Are you aware of, and using the new tweak "ToolbarKeepOff" as mentioned in http://www.xyplorer.com/xyfc/viewtopic. ... 207#p44207?

j_c_hallgren wrote:Are you aware of, and using the new tweak "ToolbarKeepOff" as mentioned in http://www.xyplorer.com/xyfc/viewtopic. ... 207#p44207?

Just edited that setting using TextPad to 250 with XY closed. When it restarted EVERYTHING was messed up - black tree and list view background colour, window size postage stamp size etc. Fortunately I have a recent backup of my settings!

I take it that was not supposed to happen with that tweak?

If the tweak worked would it have done what I was requesting?

Thanks.

Pete

petersboulton wrote:

j_c_hallgren wrote:Are you aware of, and using the new tweak "ToolbarKeepOff" as mentioned in http://www.xyplorer.com/xyfc/viewtopic. ... 207#p44207?

Just edited that setting using TextPad to 250 with XY closed. When it restarted EVERYTHING was messed up - black tree and list view background colour, window size postage stamp size etc. Fortunately I have a recent backup of my settings!

I take it that was not supposed to happen with that tweak?

If the tweak worked would it have done what I was requesting?

Thanks.

Pete

I guess TextPad did something bad to your INI... maybe it does not support UTF-16 files?

admin wrote:<snipped op post..>
I guess TextPad did something bad to your INI... maybe it does not support UTF-16 files?

Sorry, I think you are right about Textpad. I just tried the same operation in Notepad++ and the result in XY was just what I had been requesting!

Thanks for the tip! Shame about Textpad too - it's payware and good old freeware Notepad++ came up trumps!

Pete

Nothing wrong with TextPad.
It supports UTF-16 and I use it as my standard text editor. I just edited an XY ini file without any problem.
It's the way you have it configured. You can set the save format to be either the same as the load format or to always save in the same format, regardless of what the load format is. As well as different encoding it will save in Mac, UNIX and PC formats.
I assume you're using TextPad5 not 3.

Gandolf wrote:Nothing wrong with TextPad.
....
I assume you're using TextPad5 not 3.

Yes, TextPad 5.3.1. I've always loved it because it is so rock solid versus the freeware options although Notepad++ seems really good too and perhaps has better functionality these days. Plus, I paid for TextPad so I'm definitely going to use it!

I guess you are right - I see Textpad offers the following encoding options:

ANSI
DOS
UTF-8
Unicode
Unicode (big endian)

As a matter of interest, which is "UTF-16"?

Thanks for taking the trouble to respond - appreciated!

Pete

UTF 16 LE equals Unicode on Windows. So "Unicode" is correct.

Just to expand...
Unicode refers to UTF-16LE and Unicode (big endian) to UTF-16BE. It's the order in which the two bytes are stored. Windows normally uses little endian (UTF-16LE).
If you saved the file as big endian, I would have hoped that XY just ignored the ini file and loaded the default.

Gandolf wrote:Just to expand...
Unicode refers to UTF-16LE and Unicode (big endian) to UTF-16BE. It's the order in which the two bytes are stored. Windows normally uses little endian (UTF-16LE).
If you saved the file as big endian, I would have hoped that XY just ignored the ini file and loaded the default.

True! It would help me to fix this if you'd (petersboulton) send me the messed up INI file.

It's easy to reproduce:

Edit an XY ini file in an editor that will save as UTF-16 big endian (UltraEdit will do it).
Now try to use that ini file in XY.

The same problem occurs if the file is in UTF-16 no BOM.

It looks like it's something to do with the way you check the BOM.

Gandolf wrote:It's easy to reproduce:

Edit an XY ini file in an editor that will save as UTF-16 big endian (UltraEdit will do it).
Now try to use that ini file in XY.

The same problem occurs if the file is in UTF-16 no BOM.

It looks like it's something to do with the way you check the BOM.

Yep, right. Next version will be better.