topbanner_forum
  *

avatar image

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

Login with username, password and session length
  • Monday March 30, 2020, 4:34 am
  • 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.


Messages - xcopy [ switch to compact view ]

Pages: prev1 2 [3] 4next
51
LaunchBar Commander / Re: McAfee again. Don't ask.
« on: August 04, 2009, 12:30 PM »
I'd recommend F-Secure Client Security because it's reliable and highly configurable. If it only would consume less memory and run faster on slow machines.

52
LaunchBar Commander / Re: McAfee again. Don't ask.
« on: July 09, 2009, 06:42 AM »
Thanks.

McAfee and the rest of these retarded, lazy, irresponsible antivirus companies can go to hell.
;D
But what would we do without McAfee? Sitting lazy all day in front of a working computer without any thrilling experience of what possibly could go wrong.

53
LaunchBar Commander / McAfee again. Don't ask.
« on: July 09, 2009, 05:48 AM »
It's been a while since these false positives by McAfee.
Now I just got the message about a virus found in Launchbar Commander. "tool-nir-cmd".  I assume this is deliberately in the package for some new features?

54
This thread might be 2 years old but let me say anyway: level rocks!  :Thmbsup: :Thmbsup: :Thmbsup:
Thanks a lot justice!

55
LaunchBar Commander / Re: Can't run 1.70.01
« on: October 23, 2008, 02:11 AM »
Yes, works fine now. Thanks for the quick fix.

56
LaunchBar Commander / Re: Can't run 1.70.01
« on: October 21, 2008, 06:17 AM »
Currently I don't use docks at all but only the tray icon and menus.

57
LaunchBar Commander / Can't run 1.70.01
« on: October 21, 2008, 05:24 AM »
After updating to the new 1.70.01 version I can't run LaunchBar Commander anymore.

All I get after starting is a window saying
"There are no LaunchBars/Docks or Tray Menus currently visible in the configuration file.
Press the button below to create some new ones and configure options. <Configure Now>"
When I press that button my mcf-file is opened and I can see all my nodes still available and activated. Changing something and saving doesn't help; when I close that window I only get that message box again.
Help?

58
Thanks a lot mouser for going through all the trouble for us.  :up:

I had that false positive today with Launchbar Commander.
But this is developing into a workflow: Starting the PC, checking what McAffee killed today, visiting this forum, feeling with you, loading the extra.dat file, restarting the system, resinstalling the deleted program, feeling warm and cozy again and thinking of the good old days when I used F-Secure.  ;)

59
Thanks for the quick cure, mouser. Running Launchbar Commander with the new Extra.dat works fine.  :Thmbsup:

60
LaunchBar Commander / Re: New feature
« on: January 08, 2008, 04:54 AM »
I understand the request but for tiny menus this might be annoying to wait until the items appear.
Personally I like the absence of a delay very much which could change when I go using bigger menus.

So maybe a configuration option for each menu node would be a good idea.
( ) Flyout-delay in ms: ______
( ) Click to fly out

That way we'd have configurable Flyout-times (0ms would be "no delay") and the click as alternative.

[Happy new year, by the way. Keep up your good work, mouser!  :Thmbsup:]

61
Screenshot Captor / Re: Some bugs in v2.36.03
« on: September 30, 2007, 12:39 PM »
Hi mouser, good to hear. Thanks for the quick response.

62
Screenshot Captor / Some bugs in v2.36.03
« on: September 30, 2007, 12:22 PM »
Running SSC v2.36.03 the program crashes in a special case:
1. Go to your browser or any other program and copy an image to your clipboard
2. Launch SSC and choose "Paste clipboad image/object as new object"
3. When you see the pasted image, still selected, choose "Crop to selection"
4. Choose "Flatten all objects to background"

This gives me an "Access violation at address 004AE63D in module 'ScreenshotCaptor.exe'. Read of address 00000140".
I found that this doesn't happen when you skip "Crop to selection"

Furthermore I noticed another bug when testing this: it wasn't easy to perform step #2
"Paste clipboad image/object as new object" works sometimes, sometimes (mostly) not. I got the feeling that going to the menu and choosing "Paste clipboad image/object as new object" mostly works but when you hit the correspoding keyboard shortcut (ctrl-v) the image shows for the part of a second and then disappears. But I couldn't confirm this; in the latest tests, this paste-function never worked in both variations.

63
LaunchBar Commander / Re: Dock-Item-behavior
« on: April 26, 2007, 12:05 PM »
Wonderful! Thanks!  :Thmbsup:

64
LaunchBar Commander / Dock-Item-behavior
« on: April 26, 2007, 06:42 AM »
Currently, I have a dock in my tray that contains a folder. When I hover the dock item the folder item appears. When I further hover over the folder-item's icon, LBC reads and displays the folder's content.

What I want to achieve is that a folder's content is read when I hover over an icon in the tray.

Would it be possible that in a future version if a dock only contains one single item (in my case a folder) the dock could act like that containing item? Then I could make e.g. two docks and assign one folder each. That would be a quicker access than one dock with two folders.

65
LaunchBar Commander / Re: Not appearing from autohide
« on: March 12, 2007, 04:32 AM »
I just started using Launchbar Commander (btw: :Thmbsup:) and also found that irritating at first.
But after using it for a day I think there should be an option to *only* unhide the bar when clicking that thin border. Reason is that when you quickly move your mouse to the right to scroll in a window there's a high chance that you touch the right edge on the screen and the bar appears unintentionally.

66
Screenshot Captor / Re: Non-stop refreshing
« on: February 09, 2007, 05:09 AM »
Nothing special here. Tested on WinXP pro and home with different themes.
As lanux wrote: apparently it's the custom folder we have in the screenshot directory.

I just played around a bit (deleted the custom folder, created a new one, recreated the old one) and now the refreshing is gone.
Instead I  am getting that second error message I posted with each SSC start. The number of elements in this message correspond to the number of screenshots in my default screenshot directory.
 :tellme:

67
Screenshot Captor / Re: Non-stop refreshing
« on: February 09, 2007, 02:48 AM »
Same here.

1) I placed an "Archive" folder in my standard screenshot directory.
The updating makes the pane flash every 4 seconds and never stops flashing. I'm getting wooozy ;)

2) Additionally it steals the focus.
1. After opening SSC choose "MoveTo... > Configure MoveTo Folder List"
2. Place Cursor in the MoveTo Folders box
3. Wait a couple of seconds till the left pane refreshes
4. The options window is gone

3) And a third problem with this pane:
When I try to drag and drop an image to my Archive folder I get the error
"Access violation at address 00779523 in module 'ScreenshotCaptor.exe'. Read of address 00000330"
and SSC crashes.

After the restart I got
"The work item queue of the TWorkerThreadPool should be empty now, nut the number of elements were: 2 (C:\Libs\BCB6\JAMSoftware\ShellBrowser\BCB6\lib\ThreadPool.pas, line 820)"
(I don't have C:\Libs\ so there's something hardcoded?)



68
Screenshot Captor / Re: Opening the SSC window maximized
« on: September 10, 2006, 09:51 AM »
Just downloaded the latest beta. It works half.
It's a bit complicated to describe because the behaviour depends on what you do right after the start and in which state the program is closed:

1) Action right after the start
I closed SSC maximized and restarted it.
Two different behaviours from that point:
a) When I restore the main window with the right click command or a doubleclick it displays maximized.
b) When I take a screenshot right after the start the main window automatically displays non-maximized afterwards.

2) State in which SSC is closed
I have the option "Close to tray" checked. I guess this is somehow related to this window issue because I found that this option only works when SSC is closed while the main window is already closed to tray (with right-click > exit). When the main window is visible, SSC always starts with a visible window.




69
Screenshot Captor / Re: Opening the SSC window maximized
« on: September 09, 2006, 08:55 AM »
Thanks!  :)

70
Screenshot Captor / Opening the SSC window maximized
« on: September 05, 2006, 03:39 AM »
I usually let the Screenshot Captor start into the tray.
After taking the snapshot the main window appears.

The subsequent editing/resizing/whatever mostly needs a maximized window but SSC always shows a non-maximized window. Currently I'm either maximizing each session or I am using the workaround to resize the window to the maximum amount (which SSC remembers between sessions), but an option to open the SSC window maximized after having taken the screenshot would be nice.

71
Screenshot Captor / Re: Navigation Panel changes
« on: July 05, 2006, 12:07 PM »
Very much appreciated, thanks :)

72
Screenshot Captor / Re: German version
« on: July 05, 2006, 09:30 AM »
If it gets to German, you can count me in, would be glad to help.

@jeutix: especially German will be interesting because most expressions are a lot longer than in english. I saw that in the XnView localisation. Rather funny to search for suitable translations that aren't truncated.

73
Screenshot Captor / Re: 2.18.01 CTRL-D hotkey
« on: July 05, 2006, 09:23 AM »
:Thmbsup: Seconded

74
Screenshot Captor / Navigation Panel changes
« on: July 05, 2006, 09:07 AM »
The Navigation Panel is a nice way when one needs to crop images or when you make selections for any purpose.

I found it a bit confusing that the red crosshair alwas points exactly in the middle of a pixel, not on the boundaries of the pixel. When cropping or selecting the most important thing is to know which pixels are inside the selection and which ones are outside. So I always wonder if that pixel is in or out.

Instead of the current display (left side) I would suggest to make it like this (right side):
http://img83.imageshack.us/img83/5358/current1bj.gif
http://img148.imageshack.us/img148/8143/mockup6fu.gif


In the second image the crosshair aligns to the edges of a pixel. Additionally, the crosshair isn't dotted but solid and the grid isn't black but silver (both for better visibility). Should be a lot easier to select or crop this way.
What do you think?

Edit: I forgot to turn some black grid-pixels from black to silver in the altered image but I guess you get the idea.

75
Screenshot Captor / Re: 2.18.01 CTRL-D hotkey
« on: July 05, 2006, 08:39 AM »
Thanks. The always-confirm-option seems to be a good idea, though. Maybe this option could only affect the "deletion by hotkey" which is a far more dangerous thing than "deletion by menu". Deletion by menu won't happen by fault, I guess.

Pages: prev1 2 [3] 4next