The ultimate comms-tab - Page 4

zorlac · 09-15-2006, 09:49 AM

FYI - "hidden" tabs have been added to the latest development build and working well. Currently working on tab select/deselect macros, then will move onto the "repeat macro" function...

AndyHill · 09-15-2006, 10:52 PM

I did a bit of testing with the comms-system thingy by modifying the pacificfighters profile that came with TB. Anyone interested (and who wouldn't be?) can download my test version from http://www.student.oulu.fi/~ailomaki/tb/commstest.zip

Go to the comms-tab and start clicking. One of the problems I noticed is that the TB back-function isn't exactly like the one in a web browser, for example. If I click back in one tab and again in the next I'll end up in an endless loop instead of going back to where I was earlier. I can get around this on many occasions, but there are a few tabs that don't have properly working back-buttons.

Another issue is that it would be nice to be able to send function "comms cancel" when I exit any of the comms-group tabs, but only when I go to a tab that doesn't belong to the comms-group (I don't want to cancel comms when going from one comms-level to another). This isn't exactly a vital feature, but perhaps nice to have.

zorlac · 09-16-2006, 10:00 AM

Quote:

Originally Posted by AndyHill

Go to the comms-tab and start clicking. One of the problems I noticed is that the TB back-function isn't exactly like the one in a web browser, for example. If I click back in one tab and again in the next I'll end up in an endless loop instead of going back to where I was earlier. I can get around this on many occasions, but there are a few tabs that don't have properly working back-buttons.

I read this last night, and you are right... i`ll implement an unlimited history of tabs. Multiple presses of a buton with "select_tab = tb

revious" will go back through the entire list. Already worked out how to do it, so it shouldnt be too hard.

Quote:

Another issue is that it would be nice to be able to send function "comms cancel" when I exit any of the comms-group tabs, but only when I go to a tab that doesn't belong to the comms-group (I don't want to cancel comms when going from one comms-level to another). This isn't exactly a vital feature, but perhaps nice to have.

tab groups.... that will be hard, but i`ll add it to the to-do list. No promises, havent had time to think about how to make it work.

AndyHill · 09-16-2006, 10:34 AM

Yay, tab groups next week or earlier.

One more issue that came to my mind (so it should be a relatively small issue) while coding the fantastic comms-supersystem was tab-level modularity for the design. My design already sort of supports it, the only thing missing is a "tab definition file" from the supercomms root directory. The TB Toolkit could perhaps look at the file and add the tab with all of its functions to a specified profile.

I know this is a pretty big deal, but it might be important for future developement. As the profiles grow bigger and more complex their management isn't going to get any easier. RWR, radar, stores management etc. are probably going to be integrated TB modules in the next release, but what if someone wants to add my fantastic supercomms system to his own profile? Even with the toolkit's help creating profiles from scratch is a lot of work and a higher level of modularity might make it easier for people to customize their touchy-feely experience.

zorlac · 09-16-2006, 10:53 AM

I think WBK mentioned recently that he had been thinking about import/export of tabs from the toolkit, allowing export of tabs from one profile, then import to another profile. I`ll let WBK take up the story on this one...

right now, i`m doing something I havent done in a LONG time... i`m actually USING TouchBuddy for gaming (lomac flights), rather than coding it.... man, its been so long since I`ve flown

09-15-2006, 09:49 AM	#31 (permalink)
zorlac Creator Join Date: May 2006 Location: Cambridge, UK Posts: 1,612	FYI - "hidden" tabs have been added to the latest development build and working well. Currently working on tab select/deselect macros, then will move onto the "repeat macro" function... __________________ (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy)

09-16-2006, 10:53 AM	#35 (permalink)
zorlac Creator Join Date: May 2006 Location: Cambridge, UK Posts: 1,612	I think WBK mentioned recently that he had been thinking about import/export of tabs from the toolkit, allowing export of tabs from one profile, then import to another profile. I`ll let WBK take up the story on this one... right now, i`m doing something I havent done in a LONG time... i`m actually USING TouchBuddy for gaming (lomac flights), rather than coding it.... man, its been so long since I`ve flown __________________ (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

09-15-2006, 10:52 PM	#32 (permalink)
AndyHill Junky Join Date: Aug 2006 Posts: 97	I did a bit of testing with the comms-system thingy by modifying the pacificfighters profile that came with TB. Anyone interested (and who wouldn't be?) can download my test version from http://www.student.oulu.fi/~ailomaki/tb/commstest.zip Go to the comms-tab and start clicking. One of the problems I noticed is that the TB back-function isn't exactly like the one in a web browser, for example. If I click back in one tab and again in the next I'll end up in an endless loop instead of going back to where I was earlier. I can get around this on many occasions, but there are a few tabs that don't have properly working back-buttons. Another issue is that it would be nice to be able to send function "comms cancel" when I exit any of the comms-group tabs, but only when I go to a tab that doesn't belong to the comms-group (I don't want to cancel comms when going from one comms-level to another). This isn't exactly a vital feature, but perhaps nice to have.

09-16-2006, 10:34 AM	#34 (permalink)
AndyHill Junky Join Date: Aug 2006 Posts: 97	Yay, tab groups next week or earlier. One more issue that came to my mind (so it should be a relatively small issue) while coding the fantastic comms-supersystem was tab-level modularity for the design. My design already sort of supports it, the only thing missing is a "tab definition file" from the supercomms root directory. The TB Toolkit could perhaps look at the file and add the tab with all of its functions to a specified profile. I know this is a pretty big deal, but it might be important for future developement. As the profiles grow bigger and more complex their management isn't going to get any easier. RWR, radar, stores management etc. are probably going to be integrated TB modules in the next release, but what if someone wants to add my fantastic supercomms system to his own profile? Even with the toolkit's help creating profiles from scratch is a lot of work and a higher level of modularity might make it easier for people to customize their touchy-feely experience.