Keyboard resize of grids conflict with Default Folder X

[miyazakigrognard]

Model: Apple iMac (iMac8,1)
OS: Mac OS X 10.5.8
CPU: Intel Core 2 Duo 2.8 GHz
Memory: 2 GB
Video: ATI Radeon HD 2600 Pro
VASSAL: 3.1.13
Java: 1.5.0_22 from Apple, Inc.
Module: any

When using the keyboard to manually resize grid (hex or rectilinear) dimensions, the vertical key combination (CTRL + Up/Down Arrow) does nothing. If the speed-up (SHIFT) key is press, then it does respond (sped up, of course). There is no corresponding trouble in either the horizontal, or horizonatl/vertical repositioning of grids. Only vertical resize.

EDIT: On a sudden hunch, I suspected the third-party system extension, Default Folder. Sure enough, when I disable this, the problem goes away. I will report this also to St. Clair Software (makers of Default Folder). Hopefully the conflict can be traced from one end or the other.

mac

[Brent_Easton]

No apparant problems on Windoze. Can someone else on a Mac give this a try?

Thanks,
Brent.

*********** REPLY SEPARATOR ***********

On 25/01/2010 at 7:29 PM miyazakigrognard wrote:

Model: Apple iMac (iMac8,1)
OS: Mac OS X 10.5.8
CPU: Intel Core 2 Duo 2.8 GHz
Memory: 2 GB
Video: ATI Radeon HD 2600 Pro
VASSAL: 3.1.13
Java: 1.5.0_22 from Apple, Inc.
Module: any

When using the keyboard to manually resize grid (hex or rectilinear)
dimensions, the vertical key combination (CTRL + Up/Down Arrow) does
nothing. If the speed-up (SHIFT) key is press, then it does respond (sped
up, of course). There is no corresponding trouble in either the
horizontal, or horizonatl/vertical repositioning of grids. Only vertical
resize.

I am unable to think of any possible software conflict or system-wide
keyboard shortcut setting which can account for this. To my knowledge (and
extensive checking) I do not use CTRL + Arrow keys in general (up/down in
specific) for any other programme or third-party system extension (all of
which I disabled, just in case, to test that particular theory).

mac

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[jimcot]

Tried it on a macbook running snow leopard and control-up/down arrow did resize the grid.

[miyazakigrognard]

@jimcot

Tried it on a macbook running snow leopard and control-up/down arrow did resize the grid.

See my main post again: edited to reflect my having discovered the cause. I have also reported it to St. Clair Software, makers of Default Folder. No response from them as yet.

Thanks!

mac

[tar]

On Jan 26, 2010, at 1:40 PM, Brent Easton wrote:

No apparant problems on Windoze. Can someone else on a Mac give
this a try?

I just tried this on a G4 Titanium laptop.
Mac OS X 10.4.11, Java version 1.5.0_19
It worked fine in that version

I can’t test on OS 10.5 or Intel right now. (It’s a long story…)

Thanks,
Brent.

*********** REPLY SEPARATOR ***********

On 25/01/2010 at 7:29 PM miyazakigrognard wrote:

Model: Apple iMac (iMac8,1)
OS: Mac OS X 10.5.8
CPU: Intel Core 2 Duo 2.8 GHz
Memory: 2 GB
Video: ATI Radeon HD 2600 Pro
VASSAL: 3.1.13
Java: 1.5.0_22 from Apple, Inc.
Module: any

When using the keyboard to manually resize grid (hex or rectilinear)
dimensions, the vertical key combination (CTRL + Up/Down Arrow) does
nothing. If the speed-up (SHIFT) key is press, then it does
respond (sped
up, of course). There is no corresponding trouble in either the
horizontal, or horizonatl/vertical repositioning of grids. Only
vertical
resize.

I am unable to think of any possible software conflict or system-wide
keyboard shortcut setting which can account for this. To my
knowledge (and
extensive checking) I do not use CTRL + Arrow keys in general (up/
down in
specific) for any other programme or third-party system extension
(all of
which I disabled, just in case, to test that particular theory).

mac

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/listinfo/
messages_forums.vassalengine.org

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[tar]

On Jan 26, 2010, at 4:21 PM, miyazakigrognard wrote:

See my main post again: edited to reflect my having discovered the
cause. I have also reported it to St. Clair Software, makers of
Default Folder. No response from them as yet.

Now I see this.

I read the message through the EMail link, which doesn’t do anything
if the original message is edited…

Glad you found the solution.

---

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

[miyazakigrognard]

This just in from Jon at St. Clair Software:

Just a hunch - do you have a Logitech mouse? If you do, please remove this file:

/Library/ScriptingAdditions/LCC Scroll Enhancer Loader.osax

Then turn on Default Folder X, quit VASSAL, launch VASSAL again, and test for the bug.

Did as directed and the problem goes away. I presume at this point it’s up to you and/or them to take the matter up with Logitech.

Cheers!

mac

[miyazakigrognard]

@miyazakigrognard

This just in from Jon at St. Clair Software:

Just a hunch - do you have a Logitech mouse? If you do, please remove this file:

/Library/ScriptingAdditions/LCC Scroll Enhancer Loader.osax

Then turn on Default Folder X, quit VASSAL, launch VASSAL again, and test for the bug.

Did as directed and the problem goes away. I presume at this point it’s up to you and/or them to take the matter up with Logitech.

Cheers!

mac

Actually, deleting that OSAX has cleared up a good number of other issues I’ve been having with scrolling/zooming VASSAL windows. Bloody Logitech – apparently they have long since been aware of bugginess in that file, but have not fixed it up.

mac