![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
|
#12 (permalink) | |
|
Junky
Join Date: May 2006
Location: Nottingham - UK
Posts: 87
![]() |
Quote:
try gamecomander2, it dosnt require training, and works very well |
|
|
|
|
|
|
#13 (permalink) |
|
Toolkit Creator
Join Date: May 2006
Location: On your Six!
Posts: 1,864
![]() |
I have also been using GC2 for about 5 years now with no major problems. I like it a lot. But it's too expensive now I think. I got GC1 for about $29-39, and later a free upgrade to GC2.
__________________
(a.k.a. Snacko) Touchscreen: Innovatek TM-868 8"; Running Local Mode on XP Pro ![]() |
|
|
|
|
|
#15 (permalink) |
|
Junky
Join Date: Aug 2006
Posts: 97
![]() |
Ok The new fantastic hidden comms-feature has been in planning stage for a while and I came up with a couple of problems. Maybe some solutions as well, but I'm better at problems.
First of all I'm going to need tabs that only change the content of the comms-tab, they wouldn't appear on the tabs list. That's what we discussed earlier. However, it would also be useful to have an option to send a key when the player chooses the tab. I have no idea if this is actually already in the program or if it's planned. I just think it would be neat to automatically send the "comms" key to the game when entering the supercomms tab so that the first level of the comms menu is immediately visible when they enter. More importantly I'm going to need a way to send the "exit comms" -keypress when the user exits the comms-tab. That's probably the only way to syncronize the supercomms properly. When the user goes to some other tab the comms tab will reset its status and so will the comms system in the game. This would also mean that at least in my configuration there would be a "master tab" and "sub tabs. Only the master tab would be visible in the tabs list. Now when the user exits the special tab its status would either remain as it was on exit or revert back to the master tab default status (like in the comms-menu). The system could be used for example in an "MFD" -tab, which would have radar, TWS or Weapon subsystems. Or a comms-menu like mine. |
|
|
|
|
|
#16 (permalink) | |
|
Dealer
Join Date: Jul 2006
Location: North Las Vegas
Posts: 225
![]() |
Quote:
Shoot is almost perfect for me. Might be inflection, or soundcard, but once you get one that works, it's pretty cool. ![]()
__________________
![]() Setup: Core2 Duo, 7600GT, XP Pro, TM-868 touchscreen, local mode, latest version of TouchBuddy... Oh, and a DETROIT TIGERS paint job (that makes it run FASTER!!!) |
|
|
|
|
|
|
#17 (permalink) | |||
|
Creator
Join Date: May 2006
Location: Cambridge, UK
Posts: 1,612
![]() |
Quote:
It would mean some heavy duty code changes, because the tab system relies on the tab actually being "real" and visible rather that "virtual" and not displayed.Quote:
Quote:
__________________
![]() ![]() (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy) |
|||
|
|
|
|
|
#18 (permalink) |
|
Junky
Join Date: Aug 2006
Posts: 97
![]() |
Ok I'm holding my breath as of this moment.
It would already help a lot if those tabs wouldn't appear in the tabs list, since I don't want the user to have direct access to them. Tha would kind of mess the comms system completely. If the tabs are hidden from sight and you can send command on tab entry and exit the only problem I can see at the moment with the aforementioned system is that I'd neet to know when the user exits any of the comms tabs to any of the other tabs.After that operation I'd need to reset the comms system status so that the original default comms tab appears in the tabs list in its original status. |
|
|
|
|
|
#19 (permalink) |
|
Creator
Join Date: May 2006
Location: Cambridge, UK
Posts: 1,612
![]() |
was thinking about this "hidden tabs" issue yesterday while sitting on the beach, and think I have a workable option that will do the job.... I will start looking at it over the weekend
__________________
![]() ![]() (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy) |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|