topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Friday April 26, 2024, 5:34 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - elbitjusticiero [ switch to compact view ]

Pages: [1]
1
I've been using LBC for a long time now and I'm so happy with it. A few days ago I had a catastrophical Windows 8.1 failure and I had no option but to update to Windows 10. Now all my LBC menus are too big, consuming lots of space, instead of the nice compact view I had before.

It's possible that I'm not remembering my LBC configuration very well, but for the life of me, I can't find a combination of options that allows me to get the previous behaviour.

I basically have folder nodes in my toolbar, all of them in a single "menu" dock. This dock is configured to have large icons for the nodes but small icons for the menu items. The menus seem to have pretty large icons, though. And now I have to scroll endlessly to get to what I want, as opposed to when I used LBC on Windows 8.1 where almost every menu fit on the screen.

Is this something about Windows, or do I need to change some settings in LBC?

2
LaunchBar Commander / Bug with filenames (accented characters)
« on: July 02, 2020, 06:11 AM »
Hi everyone! First of all, mouser, thanks for this wonderful piece of software. I had used a couple of launchbars and even programmed my own before finding this one which is near-perfect. It now lives permanently at the top of my screen.

I wanted to point out a bug (or lack of a feature) when using folder nodes. In this case, filenames with accented letters (á, Ó, etc.) are interpreted wrongly: the characters come out as a´, O´, etc. This is not a cosmetic issue: clicking on the files brings up an error because it can't be found under that name.

Interestingly, folder names don't have this problem: I can have a path like, say, E:\Revistas\Nueva Dimensión\ND19.epub and the file will open fine. The issue only comes up with the file names.

It also happens for some files and not for others. I can't pinpoint a fundamental difference, but it's there.

Pages: [1]