[LOGic] Misc. Stuff RE 2 MONITORS

K0DAN k0dan at comcast.net
Fri Oct 21 12:26:08 EDT 2011 

Running Windows 7 Ultimate X64 with LOGIC 8 here. Use ATI 5670 Radeon 
graphics card with two 24" monitors. Via the graphics card/Windows they are 
set up as "Extended Displays", that is, I have two 24" screens which 
comprise one big desktop.

Only the "primary" display has a toolbar/taskbar at the bottom. Any open 
apps can be dragged from one screen to another, and if the system closes 
down properly, Windows will remember the position of the open applications. 
Works slick.

As to LOGIC, I cluster my logging, callbook, info, and spot screens together 
(one big LOGIC window) on the second monitor. As long as I have clicked the 
mouse (actually a trackball in my case) "focus" onto a LOGIC screen, the 
mouse buttons & wheels move & scroll just fine within LOGIC. If I 
point/click on another application, then the "focus" changes to the other 
application, no matter what screen it's on.

Perhaps I am not understanding the problem correctly (could you summarize if 
you want me to try again?) but everything seems to be working fine here, 
using the two monitors.

73
dan
k0dan



-----Original Message----- 
From: Dennis
Sent: October 20, 2011 08:17 PM
To: logic at mailman.qth.net
Subject: Re: [LOGic] Misc. Stuff

Ok, strange.  I am curious if it happens to everyone.  I have a second
monitor I can hook up & try it. But I won't be able to do anything about
it.  There is no code in LOGic to handle multiple monitors (it has no
idea if it is in another monitor or not), and no code to handle the
mouse wheel either for that matter. Windows does it all.

Tnx & 73,

Dennis WN4AZY

On 10/20/2011 8:17 PM, Ben Hatheway N6FM wrote:
> Dennis:
>
> Thanks for the reply. To clarify, the scrolling of the spot log window 
> issue
> is not whether or not the window is "in windows desktop". It is run as a
> separate window in all cases. I run all windows "in desktop" and they are
> spread out over three monitors.  The main window of Logic is compressed 
> down
> to a small block in the corner of the screen.  As a test, I dragged the
> "other QSO's" form to another monitor (it is full of T32C QSO's so there 
> is
> a scroll bar) and it didn't scroll with the mouse wheel either. I dragged
> the right 1/4 of the form back to the main monitor so that it straddled 
> two
> monitors and when the mouse was on that portion of the form that was on 
> the
> main monitor, it scrolled fine.
> For comparison, I.E. 9, Firefox, Chrome, etc all will scroll with the 
> mouse
> wheel if placed on any monitor here.
>
> Thanks again for the reply on the other issues.
>
> 73
>
> Ben
>
>
>> -----Original Message-----
>> From: logic-bounces at mailman.qth.net [mailto:logic-
>> bounces at mailman.qth.net] On Behalf Of Dennis
>> Sent: Thursday, October 20, 2011 4:57 PM
>> To: logic at mailman.qth.net
>> Subject: Re: [LOGic] Misc. Stuff
>>
>> Hi Ben:
>>
>> On 10/20/2011 2:13 PM, Ben Hatheway N6FM wrote:
>>> I have been a Logic  user since Logic 5 and really enjoy the
>>> versatility and easiness to configure and make changes. There are,
>>> however some minor annoyances  to which some attention might be paid.
>>>
>>>
>>>
>>> 1.       When running the spot log on a monitor other than the main one,
> the
>>> spot log cannot be scrolled with the mouse thumbwheel. If I drag one
>>> end of the spot log to the main screen, I can scroll the spot log with
>>> the mouse wheel from the end that is on the main screen. This occurs
>>> if the video card is the same for each monitor or not. Thumb scrolling
>>> only works from the main screen.
>> I don't have a second monitor, but putting the spot log window IN WINDOWS
>> DESKTOP makes no difference here -- it works  At any rate, there isn't
>> anything I can do -- We have no control over what Windows does when
>> moving between monitors.  Maybe an updated video driver will work.
>>
>>> 2.       DX scape window often returns with "File too small" errors.
> This
>>> might be attributed to a problem with the web site, however,
>>> re-downloading often works, if not, closing the form and reopening it
>>> works EVERY TIME. Too coincidental to be a website problem IMHO.
>> That would typically be the case.  However, I have seen a case on one
> guy's
>> machine where IE simply failed to load the whole page after logging in. 
>> I
>> have not found a cause.  A lot of that is getting rewritten, so that may
> help.
>>>
>>> 3.       Occasionally when closing the program, it will ask if I want to
>>> save the log, even if it has already been saved. If I select no, the
>>> program returns back with all the previously used forms open.
>> Ok, you're using the option to prompt before saving?  See if you can
>> reproduce the problem -- something is changing a field.  I don't use that
>> option so it may well be a problem I am not aware of.
>>
>>> 4.       Alerts do not display automatically. A message window does pop
> up,
>>> but I have to click on the main log window and back to the alert window
> to
>>> see them. This can be annoying considering all the spots that have
>> appearing
>>> fast and furious for T32C. I realize I could filter the main log, but I
>>> still want to keep track of what else is going on in the world. (However
> the
>>> existing implementation of the alert might indicate that it is not
>>> practicable).
>> I see that too.  Will look at it.
>>
>>> 5.       Nice to have- Could DX Atlas show a line from my QTH to the dot
>>> representing the location of the selected DX station? TRX Manager does,
> I
>>> thought it might be nice to have one there.
>> DX station selected where? The spot log?  It does draw on LOGic's map as
>> you scroll thru spots.
>>
>>> 6.       Could the MODE field (and the band field) in the spot log be
>>> determined by the main spotted frequency instead of the offset? Too
>> often,
>>> the spotting station uses some unorthodox verbiage to indicate the split
>> and
>>> Logic cannot (nor should be expected to) decipher what is meant.
>> Sometimes
>>> it shows a 10 meter spot instead of a 15 meter spot (or something like
> that)
>>> because Logic thinks the offset is in the 10 meter band because some
>> spotter
>>> used the actual split frequency with the "UP" parameter.
>> I'll have to check my notes on that if I have any -- it would have
>> required some extra effort to use the RX freq -- there must have been a
>> reason but I don't recall why.
>>
>>>
>>>
>>> All software possesses some anomalous behavior, but even with these
>> minor
>>> annoyances, Logic still remains the best choice for fast, efficient
> logging
>>> spotting, reporting, and  flexibility I have ever used.
>> Thanks!
>>
>> 73,
>>
>> Dennis WN4AZY
>>
>>>
>>>
>>> Ben
>>>
>>> N6FM
>>>
>>>
>> __________________________________________________________
>> ____
>>> LOGic mailing list
>>> Home: http://mailman.qth.net/mailman/listinfo/logic
>>> Help: http://mailman.qth.net/mmfaq.htm
>>> Post: mailto:LOGic at mailman.qth.net
>>>
>>> This list hosted by: http://www.qsl.net
>>> Please help support this email list: http://www.qsl.net/donate.html
>>
>> __________________________________________________________
>> ____
>> LOGic mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/logic
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:LOGic at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
> ______________________________________________________________
> LOGic mailing list
> Home: http://mailman.qth.net/mailman/listinfo/logic
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:LOGic at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html


______________________________________________________________
LOGic mailing list
Home: http://mailman.qth.net/mailman/listinfo/logic
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:LOGic at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

More information about the LOGic mailing list