Input Director v1.2.2.1 EXPERIMENTAL available for download

[Shane]

Hi,

For those who aren't afraid to live on the edge, I'm making available
for public download v1.2.2.1 (Build 77).

This is an EXPERIMENTAL version that fixes a number of minor issues
and includes a couple of enhancements.

What's in v1.2.2.1:
- Fix for Vista/Win7 systems that sometimes causes them to transition
1" from the screen edge
- Workaround for a problem that can cause Windows 7 Master's to lose
the ability to transition to slaves without first 'Rescanning slaves'
or disabling/reenabling Input Director
- Fix to keyboard mapping - if the master's keyboard layout wasn't
being applied to slaves, there was a bug in that it still influenced
which key the slave system thought had been hit.
- The shared clipboard is emptied if the slave that was holding the
clipboard data is shutdown
- Now supports horizontal wheelmouse movements (n.b. both Master and
Slave O/Ses have to be Vista or newer for this feature to work)
- Reliability improvements for problematic (wireless) connections. I'm
hopeful this change will minimise double keys / missing characters /
etc.

Its this last feature that has caused me to mark this version as
EXPERIMENTAL instead of BETA.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.zip

I'll post updates to this thread if I find problems or release a new
build.

If you do download it, please contact me ( http://www.inputdirector.com/contact.html
) and let me know (good or bad) how well its working for you.

Regs,

Shane.

[pete]

Hi Shane,

Running 3 systems all connected with ID 1.2.2.1, Windows 7, Windows
Server 2008 and Windows XP.
So far, so good.

Thanks!
Pete

> If you do download it, please contact me (http://www.inputdirector.com/contact.html

[Tryingit]

Unfortunately still having problems with being unable to move from the
master to slave every so often. It then corrects itself after random
amounts of time. Rescanning makes no difference. Both systems are
windows 7.

[Shane]

Hi,

There's a new release - build 78 of v1.2.2.1 now available, for those
fearless souls willing to play with an EXPERIMENTAL version.

Build 78 includes:
- Shutdown slaves (but not master) from right-click context menu
- Reverted File copy/pastes back to using hostnames instead of ip
addresses
- increased the maximum supported monitors from 8 to 10 per system
- Windows Shell Integration

The file copy/paste change I am hoping will help some users that have
experience problems being able to copy files one way but not the
other.

The shell integration works like this:

If you right-click on a file or directory that available via a network
share, you should see an "Input Director" menu as one of the pop-up
menu items. From here you can choose to open that file/directory on
any of the other available input director systems.
If you hold down shift when clicking, then the file will be opened on
the other system and Input Director control will switch to that system
as well.


It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.78.zip

Enjoy,

Shane.

[Th3GMan]

Hi Shane,

I'm running this on Windows 7, and no bugs or anything to report as of
yet.

Just wanted to let you know it appears to be running nice and smooth.

Thanks
Dave

[Shane]

Hi,

Build 79 of the Input Director v1.2.2.1 EXPERIMENTAL version is now
available for download.

This update will (hopefully) improve the reliable communication
function, in particular to reduce jerkiness and duplicate characters
over wireless links.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.79.zip

Don't forget to upgrade the slaves before the master.

If you do test this version and did have cursor stuttering with the
previous build, can you please contact me and let me know if this
update has improved the situation.

Thanks,

Shane.

[Singularity]

Hello Shane,

GREAT WORK!!!

I just grabbed my copy and installed it right away.

Current configuration:

Master: Windows 7 Professional (Single Monitor)
Slave: Windows XP Professional SP 3 (Single Monitor)

Current Version of ID: 1.2.2.1b78

When updating (Slave first -- with reboot, Master second) the slave
keeps telling: Waiting for the master to update to newer version.
Rebooting the slave and message was gone!

Keep on coding!

Greets,

Sin

[Shane]

Hi,

Build 80 of Input Director v1.2.2.1 EXPERIMENTAL version is now
available for download.

This update includes minor tweaks to the reliable communication
feature and a new redesigned "keyboard layout" implementation. (The
keyboard layout feature allows you to use the the keyboard layout
configured on the master, when directing a slave. This is handy for
those folks who might have, as an example, a French keyboard layout on
their slave and a German keyboard layout on their master).

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.80.zip

Don't forget to upgrade the slaves before the master

Regs,

Shane.

[Shane]

Hi,

Build 81 of Input Director v1.2.2.1 EXPERIMENTAL version is available
for download.
It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.81.zip

This update includes a bug fix to the keyboard layout function that
was incorrectly handling the shift key.

A bug was introduced into v1.2.2 that stopped file copy/pastes using
the shared directory from working when copying from a Windows 7
master. This update will cause this same bug to occur on Windows 7
slaves. The workaround is to lower UAC security to its minimum
setting. I'm looking to address this bug soon in one of the next
builds.

A major new feature released in build 81 is the 'auto switch master/
slave role' option. This can be switched on from the 'Global
Preferences'. Any system that has this checkbox selected will
automatically become the master if its physically attached mouse is
used and any master with this option selected will switch to slave
mode if another master tried to control it.

The upshot of this is that if you have a keyboard/mouse attached to
your master and your slave and you turn this option on, you can use
either keyboard/mouse at any time to control any system.

For this feature to work, you must configure each machine as both a
master and a slave (so you must setup the appropriate configuration in
both the 'Master Configuration' and 'Slave Configuration' tabs.

I am keen on feedback! The way its currently set up is that if you
swap which keyboard/mouse your using, this continues controlling which
ever system was already being controlled, rather than resetting the
cursor to the newly chosen master. I'm not sure what the right
behaviour should be and I'm loathe to make that an option in itself.
I've also chosen to do the switch based on mouse movement rather than
mouse or keyboard. This was a slightly easier approach and seemed to
make sense at the time.

btw: You don't have to enable this option on all your systems - for
example, if you have 3 systems and only 2 still have keyboard/mouses
attached, you would only turn this option on, on those two and would
configure them both to be a master with the other two as slaves.

Please email me with feedback / bugs / etc: (details here:
http://www.inputdirector.com/contact.html)

Regs,

Shane.

[pete]

Shane,

Awesome!... I just installed build81 one 3 systems, two of them
potential masters, and the auto-role switch works great!

The only funky thing about it was the behavior during installation on
the slave when it saw a new master it didn't recognize and put up a
prompt, which I couldn't reply to, asking if it was ok to switch to
the new master. Other than that one time quirk, it was great!

thanks so much!

Pete

[Shane]

On Aug 24, 12:45 am, pete <pmmc...@gmail.com> wrote:
> Shane,
>
> Awesome!... I just installed build81 one 3 systems, two of them
> potential masters, and the auto-role switch works great!

I think I'm going to change auto-switch in the next build, so that
when you wiggle the mouse of another system and it changes role to the
master, that the cursor is centered on that new master.

Every time I auto-switch I find myself hunting for the cursor even
though I know it will be on whichever system I'd left it.

Regs,

Shane.

[Frank]

Shane,

I have 3 Windows 7-64-bit PC's. I installed build 81 this morning
before work and all was working fine. The 'auto switch master/
slave role' option was NOT enabled. Before leaving for work, I
powered my PC's down and powered them up when I got home, suddenly, on
the right slave a message popped up that it switched to Master mode
(auto switch option was NOT set). When I went back to the Master and
dragged the mouse to the right slave, the slave popped up that a
master wanted it to switch to slave mode and that corrected the
problem. However, after a reboot of the slave the problem
reappeared. I un-installed ID from all 3 Pc's and reinstalled Build
80; all seems to be working OK again.

[Adler, Frank]

Forgot to add that the right slave has no attached keyboard and mouse.

--
You received this message because you are subscribed to the Google Groups "Input Director" group.
To post to this group, send email to input-d...@googlegroups.com.
To unsubscribe from this group, send email to input-directo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/input-director?hl=en.

[Shane]

On Aug 24, 8:14 pm, "Adler, Frank" <adler...@gmail.com> wrote:
> Forgot to add that the right slave has no attached keyboard and mouse.

Hi Frank,

Can you try Build 82 and see if that resolves the issue.

Thanks,

Shane.

[Shane]

Hi,

Input Director v1.2.2.1 EXPERIMENTAL Build 82 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.82.zip

This build tweaks the auto-role switching - you need to move the mouse
on the slave around at least 1/10 second before it will switch to
master mode. It will also start the cursor on a newly auto-role
switched master rather than where ever it was beforehand.

The build also lets you use a single hotkey to toggle screen-edge
transitions on & off. This is for the folks who are keen to use (as an
example) the scrolllock key to toggle edge transitions.

Regs,

Shane.

[Adler, Frank]

Shane,

Unfortunately, I experience the same behavior with Build 82. After upgrading the slaves first from Build 80, each slave does not recognize the prior build's configuration settings and they initialize in Master Mode.  I then upgraded the Master to Build 82.  I then connected a temp/ KB/mouse to the right slave and configured it as a slave to run at startup for all users. Did the same for the right slave (laptop).  All OK after that.  The "auto/switch master/slave role" option is unchecked on both slaves.

I then rebooted the two slaves and they reverted back to Master Mode even though the "auto/switch master/slave role" option is unchecked on both slaves.

I am back to Build 80 and all working fine again. Perhaps the "auto/switch master/slave role" option is having an effect even when it is unchecked?  I can try to check it on each slave to see if things work normally with it enabled.

Frank 

Shane.

[Shane]

Hi Frank,

I think I can guess what the problem might be - when the slave's
initialised in master mode, Input Director stores that that system
should start up in master mode next time (it alters the startup choice
found under the 'Global Preferences').

After you've unchecked the 'auto-role switch' option, if you then
change the startup choice back to slave, it should all work normally.

It sounds like the issue is that on upgrade the slaves had a problem
with the existing configuration (did you get an error message pop-up?)
and that when they reset to the default configuration they defaulted
to startup as a master and with the auto-role switch enabled? Was that
the case?

The auto-role switch option is meant to default to off - and that may
be where the bug is.

The current design has Input Director remembering whether it is a
slave or master and what mode it should restart it, if auto-role
switching is in use. So if a system auto-switches to being a master
then it will restart in master mode next time. Ditto if it was a
slave.


Regs,

Shane.

[Adler, Frank]

Shane,

I have been using ID for the past few years (and LOVE it). I normally have only one keyboard and mouse and it is attached to the Master. With Build 81 and 82 and with the auto-role switch option NOT checked on any of my 3 computers, I am running into this problem.

To fix, I connect temp. KB/mouse to the slaves,I switch roles to slave, change configuration to startup in slave mode just like I do with all prior builds but after rebooting the slaves revert back to Master mode. 

I have never experienced an automatic switching of roles before these new builds.  If the auto-role switch is NOT checked shouldn't the new builds operate as in Build 80 and prior?  

Regs,

Shane.

[Th3GMan]

Same issue here.

Every time I boot up Input Director (build 82) on my Slave machine
tells me that it is in Master mode, and do I want to switch it to
slave mode because a system is trying to communicate with it (not the
error verbatim, but close).

So each time, I say yes, then I go in and check the setting. Set to
Slave system and Auto-Switching is off.

Then at reboot, same issue reappears.

Other than that, Input Director rocks!

> > input-directo...@googlegroups.com<input-director%2Bunsu...@googlegroups.com>
> > .

[Shane]

Hi Frank / Th3GMan,

I'm having difficulties reproducing the bug on my systems.

Could you try something for me? -

1. On your slave, open Input Director and switch to the "Global
Preferences" tab. Confirm that On Start is set to "enabled as a Slave"
and that auto-switch is off.

2. Reboot the slave

3. Open "Global Preferences" again and check if "On start" is still
set to "enabled as a slave", and that auto-switch is still off.

4. Reboot once more.

Does the problem re-occur after step 2 and after step 4?

Thanks,

Shane.

[Adler, Frank]

Shane.  I'll try it now.  I am currently on Build 80 so I'll installed 82 on slave and master.

Shane.

--
You received this message because you are subscribed to the Google Groups "Input Director" group.
To post to this group, send email to input-d...@googlegroups.com.

To unsubscribe from this group, send email to input-directo...@googlegroups.com.

[Adler, Frank]

Just upgraded slave from build 80 to 82.  After install it automatically switched itself to Master.  Now I'll update my Master from 80 to 82.

[Adler, Frank]

I updated the master from 80 to 82.  Went back to original slave that set itself to master, opened Input Director and switched to the "Global
Preferences" tab. On Start is set to "enabled as a Slave"
and auto-switch is off.  Now I'll reboot.

[Adler, Frank]

Slave reverted back to Master after reboot and after logging in. It is still configured as a slave and auto-switch off and set to run at startup. Now I'll reboot again.

[Adler, Frank]

back to master again. 

[Adler, Frank]

Shane. FYI.  After reboot of slave, I can control it from the master when slave is at a login prompt and type in my password.  After the slave logs in I lose communication from the master and the slave switches to Master.

[Th3GMan]

Yep. Same exact thing here. Back to Master every time. And I get this
exact message on what should be my slave system when I try to mouse
over:
"A master systems is communicating as if Input Director is in slave
mode. Do you wish to switch to slave mode?"

I did what you asked (even rebooted 3 times) and verified Slave was
set and Auto-switch was off...

On Aug 25, 6:33 pm, "Adler, Frank" <adler...@gmail.com> wrote:
> back to master again. [?]

>
> On Wed, Aug 25, 2010 at 7:30 PM, Adler, Frank <adler...@gmail.com> wrote:
> > Slave reverted back to Master after reboot and after logging in. It is
> > still configured as a slave and auto-switch off and set to run at startup.
> > Now I'll reboot again.
>

> > On Wed, Aug 25, 2010 at 7:23 PM, Adler, Frank <adler...@gmail.com> wrote:
>
> >> I updated the master from 80 to 82.  Went back to original slave that set
> >> itself to master, opened Input Director and switched to the "Global
> >> Preferences" tab. On Start is set to "enabled as a Slave"
> >> and auto-switch is off.  Now I'll reboot.
>

> >>>> input-directo...@googlegroups.com<input-director%2Bunsu...@googlegroups.com>
> >>>> .

> >>>> For more options, visit this group at

> >>>>http://groups.google.com/group/input-director?hl=<http://groups.google.com/group/input-director?hl=en>
>
>
>
>  323.gif
> < 1KViewDownload

[Shane]

Hi,

Input Director v1.2.2.1 EXPERIMENTAL Build 83 is available for
download.
It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.83.zip

Build 83 fixes a bug identified by Frank Adler and Th3GMan that would
cause the system to start as a master even if the on start option was
set to slave.

Thanks Frank and Th3GMan!

Regs,

Shane.

[Shawn]

Setup{
Master{
Version: v1.2.2.1.82
OS: Windows 7 Enterprise 64bit
Network: Wired / Domain
Monitors: 6
}
Slave{
Version: v1.2.2.1.82
OS: Windows XP Home SP3 32bit
Network: Wired / Non-Domain
Monitors: 1
}
};

Great work! I love the auto-switching master-slave. Also one of your
resent changes allowed me to go back to using the host name instead of
the IP address. Though I'm still trying to figure out my network on
the wireless-wired vlan hop.

Thanks again!

Shawn

[Singularity]

Hello Shane,

i love this new feature "Auto-Switch master / slave role"!!!!

This is just what i wanted to have!!!

Is this though Xmas??? ;-)

Setup{
Master{
Version: v1.2.2.1.83

OS: Windows 7 Enterprise 64bit
Network: Wired / Domain

Monitors: 1
}
Slave{
Version: v1.2.2.1.83
OS: Windows XP Professional 32bit
Network: Wired / Domain
Monitors: 1
}
};

I'm loving it!!!! :D

Sin

[Frank]

Shane,

Build 83 works like a charm! I first tested with the Auto-switch
master/slave role disabled on each of my 3 PC's and that works
normally. I have also done some basic testing with that switch
enabled and alternating use of KB/mouse connected to each PC; master/
salve roles are switching properly.

Thanks for your efforts.

Frank

[kidchunks]

GREAT APP!
Just tried out the .83 release and still having this one issue (not
sure if its a bug or not). When ever I lock the master pc (windows key
+ L), I cant transition to the slave. Same applies if both the master
and the slave are at the login prompt. It sticks to the master.
(tested on windows 7)

[Shane]

Hi,

This is a design limitation I'm looking to correct in a future
version.

Regs,

Shane.

[Shane]

Hi,
Input Director v1.2.2.1 EXPERIMENTAL Build 84 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.84.zip

Build 84 fixes a problem doing file copy/pastes across the shared
clipboard from Vista/Win7 systems
Auto-role switch messages can now be optionally suppressed

Regs,
Shane.

[Shane]

Hi,
Input Director v1.2.2.1 EXPERIMENTAL Build 86 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.86.zip

New features in build 86 includes:
- Can setup a hotkey to rescan slaves (found at the bottom of the
Master Preferences tab)
- Key Bindings (bind a key on the master's keyboard to a selected
system / key)
- If a slave fail's to respond, can set ID to inform but not 'skip'
the slave. Found under "Suppress Warnings"

Those folks that have installed Build 84 on Vista/Win7 - apologies,
but the hands-free update to build 86 won't work. You'll need to
shutdown input Director first and then run the installer.

Regs,
Shane.

[Shane]

Hi,

Input Director v1.2.2.1 Build 86 ends the 'new development' cycle. My
focus now will be on fixing bugs in preparation to promote it to BETA.

If you do download Build 86, can you please send me an email (contact:
http://www.inputdirector.com/contact.html ) and let me know if you
find a bug or if its working correctly. I really need feedback at this
stage to gauge the quality of the build.

Thanks,

Shane.

[Frank]

Shane,

I installed Build 86 on my Master and left-side slave..no issues on
those two. On my right slave, I get an ID "Fatal Error: Unable to
create or read the application's configuration". After clearing the
error, the slave/master buttons are grayed out. I did a complete
uninstall of ID and reinstall of Build 86 and still get the error.

Next I did a complete uninstall 0f Build 86 and installed Build 84.
Now the install works OK and I can control this slave normally.

BTW, the left and right slaves are running Windows 7 Enterprise 32-
bit. The master is running Windows 7 Enterprise 64-bit.

Frank

On Oct 3, 6:57 pm, Shane <sh...@inputdirector.com> wrote:
> Hi,
>
> Input Director v1.2.2.1 Build 86 ends the 'new development' cycle. My
> focus now will be on fixing bugs in preparation to promote it to BETA.
>

> If you do download Build 86, can you please send me an email (contact:http://www.inputdirector.com/contact.html) and let me know if you

[Shane]

Hi,

Input Director v1.2.2.1 EXPERIMENTAL Build 87 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.87.zip

Build 87 fixes 3 bugs:
- A fresh install could end up with a "Cannot read configuration"
message when starting Input Director
- A minor fix to the macro recorder - there was a situation which
could cause it to drop recorded keys
- A fix to a bug introduced in build 84 & 86, which would stop the
hands-free upgrade from working correctly.


For those folks upgrading from v1.2.2.1 build 84/85/86 - the hands-
free upgrade may not work properly. In which case you'll need to run
the Input Director uninstaller first and completely remove it before
installing build 87. I've put a fix into build 87 which I am hoping
will fix this problem from now on.

Regs,

Shane.

[kawaiiwolf]

Ran into an buggy state running:

Windows 7 Master w/ 1.2.2.1.87 using the "Auto-Switch" feature. USB
Keyboard/Mouse.
Windows Vista Slave w/ 1.2.2.1.87 using the "Auto-Switch" feature.
Laptop w/ Elan Smart-Driver for the touch pad mouse.

Mouse activity on the Vista Slave switches the Windows 7 to slave.
Right/Left mouse buttons work OK, but when I use two fingers to tap on
the touch pad (for a middle click), the Windows 7 system starts to act
buggy: Mouse clicks on window frames, task bar or most windows stop
functioning; most of the control has to be done via keyboard. Click
events on the desktop seem to function just fine however.

Disabling Input Director doesn't seem to rectify this situation,
disabling "Input Director Vista Service" and "Input Director Service"
don't help, nor does killing/restarting explorer via the task
manager.

The ONE thing that does work, is going the windows 7 system and middle
clicking on the USB mouse. Basically a "middle click" with two fingers
tapping the track-pad using the Elan Smart-Driver issues a mouse down
event on the slave system, but never a mouse up, causing the system to
misbehave until it gets a mouse 2 up event from some other source.

[Shane]

> Mouse activity on the Vista Slave switches the Windows 7 to slave.
> Right/Left mouse buttons work OK, but when I use two fingers to tap on
> the touch pad (for a middle click), the Windows 7 system starts to act
> buggy: Mouse clicks on window frames, task bar or most windows stop
> functioning; most of the control has to be done via keyboard. Click
> events on the desktop seem to function just fine however.

Hi Kawaiiwolf,

If you disable the auto-switch functionality and have Windows 7 to
start in slave mode and Windows Vista as the master - does the middle
click (two fingers on the touch pad) work correctly on the slave?

Regs,

Shane.

[Shane]

Hi,

Input Director v1.2.2.1 EXPERIMENTAL Build 88 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.88.zip

Build 88 fixes 1 bug:
- media keys on some keyboard could not be "bound" to another system

For those folks upgrading from v1.2.2.1 build 84/85/86 - the hands-
free upgrade may not work properly. In which case you'll need to run
the Input Director uninstaller first and completely remove it before

installing build 88.

Regs,

Shane.

[kawaiiwolf]

Nope: It seems if a master system (even temporarily) is using that set
of drivers, the Mouse 3 Up event is not sent to the slave systems, 7
or otherwise. If I plug a USB mouse into the vista laptop and use
that, the behavior does not manifest. Hence, it seems the issue has to
do with multi-touch support for laptop touch pads (running the ELAN
multitouch driver: etdware ps 2-x86)

[Shane]

Hi,

On Oct 28, 1:00 am, kawaiiwolf <kawaiiw...@gmail.com> wrote:
> Nope: It seems if a master system (even temporarily) is using that set
> of drivers, the Mouse 3 Up event is not sent to the slave systems, 7
> or otherwise. If I plug a USB mouse into the vista laptop and use
> that, the behavior does not manifest. Hence, it seems the issue has to
> do with multi-touch support for laptop touch pads (running the ELAN
> multitouch driver: etdware ps 2-x86)

Would you be willing to run a special diagnostic build of Input
Director - I'd like to see which mouse events Input Director is
trapping. It may be that the mouse-up is not being emitted in the
usual way and ID isn't seeing them.

Regs,

Shane.

[Shane]

Hi,

Input Director v1.2.2.1 EXPERIMENTAL Build 89 is available for
download.

It can be downloaded from: http://www.inputdirector.com/downloads/InputDirector.v1.2.2.1.89.zip

Build 89:
- Fixes a bug that can cause transitions to end up on the wrong
monitor
- A bound key can now have its target set to 'System with input focus'

For those folks upgrading from v1.2.2.1 build 84/85/86 - the hands-
free upgrade may not work properly. In which case you'll need to run
the Input Director uninstaller first and completely remove it before

installing build 89.

Regs,

Shane.