Feature Requests

**0l33l** · 07-30-2005, 04:42 AM

Post your feature requests here.

**justintime** · 07-30-2005, 07:59 AM

Would like the ability to play a sound (.wav) file with each button press.
Audible feedback is a MUST in a touchscreen!

I have my frontend (Centrafuse) play a wav file with each button press. When SkinBedder kicks in, I have nno audible feedback. Disaster!

**RPM_VR4** · 07-30-2005, 04:57 PM

Will do!

**0l33l** · 07-31-2005, 01:28 AM

Originally Posted by RPM_VR4

Will do!

Sounds like a job for AutoIt

**RPM_VR4** · 07-31-2005, 10:32 PM

Well, it currently will run AutoIt scripts, so yeah... you can do it with 2.999

I could add a Play([filename]) command to our scripts using TMediaPlayer though. Should I do it?

**justintime** · 07-31-2005, 11:21 PM

Not sure what you guys are proposing... I wouldn't want to have to script this in... can you natively support 'playing a wav' file upon every successful button press?

**0l33l** · 08-01-2005, 03:06 AM

Originally Posted by justintime

Not sure what you guys are proposing... I wouldn't want to have to script this in... can you natively support 'playing a wav' file upon every successful button press?

Yeh, we could.

Just thought that giving people ability to define different sound files for each button would be better

**justintime** · 08-01-2005, 08:10 AM

I would rather have ONE global wav file setting, than having to define it multiple times throughout the config.

I think most people would want the same 'click/berep' sound for every button push. Keep It Simple.

Originally Posted by 0l33l

Yeh, we could.

Just thought that giving people ability to define different sound files for each button would be better

**Bravellir** · 08-01-2005, 03:27 PM

It would be interesting to have a "toggle" behaviour on the buttons. Something like:

[B0]
X=0
Y=40
Image_S0=button.bmp ; bitmap status 0
Image_S1=buttonselected.bmp ; bitmap status 1
ImageDown= button_Down.bmp
ImageOver= button_Over.bmp
ImageDissabled= button_Down.bmp
Anchors=Bottom,Left
Command_S0=command1, command2,… ; commands status 0
Command_S1=command8, command9,… ; commands status 1

I know that there is no way for SD to know what is the status of the toggle when the client app is embedded, but even so it might prove useful.

Ex: I have SB on my car, embedding NetStumbler. I can start and stop scanning with a simple key press, Ctrl B I think. It would be great to have a good visual indication if scanning it's on or off since NS has just a small indication on the status line.

What do u think??

**RPM_VR4** · 08-01-2005, 04:44 PM

JIT: Sorry man, I don't really like it that way. Right now each button has a script like this:

command=Send(Up)

Currently, all buttons send to the Map window too. I am going to move more and more in to the command script so that people can customize it to do whatever they want. This is how it will be for V3:

Command=Play(beep.wav),Focus(Map),Send(Up)

You can either Find and Replace "beep.wav" with whatever you want, or just replace the beep.wav file. If you don't want a beep, then you can either Find and Replace "Play(beep.wav)," with "" or you can just delete beep.wav.

Bravellir: My plan is to make it so buttons can switch "skins". If you want a toggle button, you would just have 2 identical "skins" except for that one button being different. I suppose if you need multiple toggle buttons on the same screen, there could end up being a ton of "skins" to cover ever possible combination of the toggles, so I might add a more true toggle feature to the buttons, but that will come later. At least it will be possible to have a few toggles in V3.

Edit: JIT: Actually you since the Run() command will run any file that has an association, you could just Find and Replace "command=" with "command=Run(beep.wav)," and it would work right now (however, that may make WMP or whatever you have associated with .wav's popup in front of SKINbedder).