Ticket #4933 (closed Bug report: fixed)

Opened 4 years ago

Last modified 4 years ago

Pane widths reset on New Tab

Reported by: DanielBeardsmore Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Operating system type: Windows Operating system version: 5.1.2600

Description

Using 3.3.0-beta1 -- when opening a new tab, the widths of the four directory panes are reverted to defaults. These panes are the local site tree pane, local listing pane, remote site tree pane, remote listing pane. This happens with the layouts with horizontal spacing, e.g. all but classic.

Classic layout remains unaffected as it's only the horizontal layout that's reset to defaults.

Attachments

01. One tab.png Download (38.0 KB) - added by DanielBeardsmore 4 years ago.
Layout set as desired
02. Two tabs.png Download (38.9 KB) - added by DanielBeardsmore 4 years ago.
Layout as reset after opening a tab

Change History

Changed 4 years ago by codesquid

  • status changed from new to closed
  • resolution set to fixed

Fixed already, please try tomorrow's nightly.

Changed 4 years ago by DanielBeardsmore

Layout set as desired

Changed 4 years ago by DanielBeardsmore

Layout as reset after opening a tab

Changed 4 years ago by DanielBeardsmore

  • status changed from closed to reopened
  • resolution fixed deleted

Not sure you understand the problem, so I've attached a couple of screenshots taken from the latest nightly (downloaded a couple of minutes ago).

Once a new tab is opened, the directory tree columns reduce to an unusable size.

Changed 4 years ago by codesquid

  • status changed from reopened to moreinfo_reopened

Which build is it you are using?

Changed 4 years ago by DanielBeardsmore

  • status changed from moreinfo_reopened to reopened

3.3.0-beta2-nightly, build date 2009-10-30.

Changed 4 years ago by codesquid

  • status changed from reopened to closed
  • resolution set to fixed

Found the reason. Will be fixed in the next version.

Changed 4 years ago by DanielBeardsmore

I can confirm that this bug is fixed in the most recent nightly. Thanks!

Note: See TracTickets for help on using tickets.