Set speed using mouse wheel
Jared Thirsk
Kurt Siegl
> Has anyone tried mapping speed to scrolling the mousewheel up and down? (I
> googled and F3'ed the FOCS but didn't see it.) I noticed mousewheel now
> zooms in on Netrek XP -- cool (useless maybe but whatever :))
Mouse wheel is considered as button 4 and 5 so I do not know how it interfears
with the shiftedMouse feature.
However I do have a mouse button only keymap with major speed buttons as
shift and ctrl right mouse for a good reason.
# 007's extended mouse button map alows you to play with the mouse only.
# Mouse Buttons:
# Normal: torp phaser set course
# Shift: shield traktor half warp
# CNTRL: cloak pressor warp 6
# CTL-Shift: macro info lock
continuousMouse: off
shiftedMouse: on
# Using virtual keys for ship independend macro overlays.
buttonmap: 1^A2^B3^C4^D5^E6^F7^G8^H9^Ia^Jb^Kc^L
ckeymap: ^At^Bp^Ck^Du^ET^F#^Gc^Hy^I6^JX^Ki^Ll
keymap: afsDddzzxxccv%nrmm dXX0%-R++\-??wwiiIIKKOOSSVVBBUUDDee
Of corse major speed buttons bepend on the ship type, so they are overwritten
automatically.
# Special combat speed keys dependend on ship types
ckeymap-sc: ^F5^I%
ckeymap-dd: ^F5^I7
ckeymap-ca: ^F4^I7
ckeymap-bb: ^F3^I6
ckeymap-as: ^F4^I%
ckeymap-sb: ^F%^ID
> As long as one's own desired speed was highly visible, I would think this
> would increase usability, and free up both fingers during dogfighting as
> well as simplify the keymap by 4-13 keys.
As long as you are not playing DD only, ship type keymaps will help here ;-)
> Would people consider this borgish? I personally think it would/could make
> playing a tiny bit easier but in a way I am for. (To me, keys for turning
> the ship is too borgish for my comfort at the moment but it's still in my
> mind.)
That was a comon understanding yes, as far as I remember it can be turned off
by the server because of that.
> I know some people have clever keymaps with fighting/cruising/maxwarp speeds
> mapped out convenient locations, but I've never gotten around to doing that
> and instead plopped all my keys right under 4-7 in order to have access to
> speeds, but I think this might be silly (partial ulterior motive: I am
> rethinking a keymap with better access to shift/alt/ctrl keys, as well as
> keeping one of the player's hand on a home row typing position.) I also
> use keys to fire weapons, so I have spare fingers on my mouse.
Kemaps are usually one of the major key of successful play, so you definitivly
should think about this topic careful.
Oh yes I have the macros overlayed onto the mouse as well.
# Place all important macros and distess calls onto the mouse.
# Requires 007's extended mouse button map.
# Mouse Buttons:
# Normal: pop control pickup
# Shift: bombing escorting ogging
# CNTRL: defend me ack player ogg
# CTL-Shift: distress takeing carring
dist.^A.pop: %T%c->%O %l%?%n>-1%{ @ %n%}!
dist.bomb: %T%c: %?%n>4%{bomb %l @ %n%!BOMB%}
dist.^B.save_planet: %T%c->%O Emergency at %L!!!!
dist.space_control: %T%c: Danger Help Control at %l
dist.^C.pickup: WATCH %u: %t%p++ @ %l
dist.^D.bombing: %T%c: Bombing %l @ %n
dist.^E.escorting: %T%c: Escorting %p
dist.^F.ogging: %T%c: Ogging %p
mac.^G.%u: defend %c
mac.^H.%u: ACK
dist.^I.ogg: OGG %u (%t%p) near >%l<
dist.^J.help: %i (%S %T%c@%b): %?%S=SB%{SB%!%} Help! %d%% dam, %s%% shd,
%f%% fuel %E%{ETEMPED!!! %}%W%{WTEMPED!!! %}%?%a>0%{%a armies!!%!%}
dist.^K.taking: %i (%S %T%c@%b): need ESCORT going to
>%l%?%n>0%{@%n%}<%?%a>0%{, carrying %a armies!%}
dist.^L.carrying: %i (%S %T%c@%b) has %a armies on board!
Have fun,
Kurt (007)
--
Kurt Siegl / Thann 14, A-4483 Hargelsberg, Austria
Email: Kurt....@hargelsberg.at
Tel: +43 699 1 1707 1 65
Fax: +43 810 9554 192662
URL: http://www.hargelsberg.at/siegl/kurt/
Bill
# Mouse button mapping
# Button map lets you map the mouse buttons. Unfortunately, it works
in a
# different way than keymap. The format is <mousebutton> <key>. To
map
# shields onto button 1 (the left one), you would put '1s' in your
keymap.
# The buttonmap works through the keymap, so if you have shields
mapped to
# 'q', putting '1q' would make button 1 shields and not quit. Buttons
4 and
# 5 are support for Microsoft Xbuttons. If you have a wheel mouse,
the up
# wheel is button 6 and the down wheel is button 7. There is also
support
# for shifted, controled, and control-shifted mouse actions, see the
netrek
# help file for more details.
The default key for slow speed by 1 is <. The default key for
increase speed by 1 is >. So a buttonmap of 6<7> would give you the
behavior you desire. Alternatively, bind maxwarp to scroll up and
warp 0 to scroll down for better/faster responsiveness.
Bill
Trent Piepho
> --
> To post send mail here: netrek-...@googlegroups.com
> More info: http://groups.google.com/group/netrek-forever/
> Nota bene: Please be civil and treat list members with respect.
>
>