fuse-emulator-devel — Development of Fuse (the Free Unix Spectrum Emulator), the associated utilities and libspectrum, the ZX Spectrum file-format handling library.

[fuse-emulator-devel] Error after ubuntu update

[Darren C. <dar...@gm...>]

This is the error that I now encounter after the last auto update.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

fuse: error: This machine does not support the Interface 2
fuse: error initialising -- giving up!

I have tried the fuse --no-interface2 command and it still tells me there
is no support for interface 2. I have tried other emulators that use
interface 2 and have had no problems. Fuse is the best emulator I have used
and now its not working. Please advise

Re: [fuse-emulator-devel] Possible Fuse Flatpak bug - no audio on OpenSUSE 15.1

[Alberto G. <be...@ig...>]

On Mon, Aug 05, 2019 at 07:53:46AM +0100, Nicholas Harvey wrote:

> I thought I would pass on the link to a bug I have just raised
> against the Fuse Flatpak here:
> 
> https://github.com/flathub/net.sf.fuse_emulator/issues/3

> [...] I am not sure if you maintain the Flatpak but if you do this
> would be great to fix if possible.

Hi,

I'm just writing to say that I was away for a couple of weeks and did
not check my e-mail, but yes the Flatpak build is maintained and I'm
handling the bugs.

I'll continue the discussion on GitHub because this problem is
specific to Flatpak.

Thanks for the report,

Berto

Re: [fuse-emulator-devel] TTX2000S emulation

[Alistair <ali...@zx...>]

I've published a webpage about the interface including ROM images and 
everything I've been able to determine about the hardware.

https://zxnet.co.uk/spectrum/ttx2000s/

Alistair.

[fuse-emulator-devel] Possible Fuse Flatpak bug - no audio on OpenSUSE 15.1

[Nicholas H. <mob...@gm...>]

Hi

I thought I would pass on the link to a bug I have just raised against 
the Fuse Flatpak here:

https://github.com/flathub/net.sf.fuse_emulator/issues/3

Basically when running the Flatpak on OpenSUSE Leap 15.1 there is no 
sound. There is an identical bug for the Amazon Cloud Player Flatpak and 
a work-around which I have linked to in the bug report. I am not sure if 
you maintain the Flatpak but if you do this would be great to fix if 
possible.

Thanks for the work you have done on this emulator!

Best regards
Nick

Re: [fuse-emulator-devel] TTX2000S emulation

[Sergio B. <ser...@gm...>]

Hi Alistair,

On 31/7/19 23:20, Alistair wrote:
> Thanks, the other question is, should this be made optional to compile
> like I believe spectranet is for the targets that have no socket.c in
> compat?

Yes. Users can also disable networking dependencies at configure time
with --disable-sockets option


> Something like an #ifdef BUILD_TTX2000S around everything and stuff in
> the autotools source (configure.ac?)
Yes, that's the idea. If you are not comfortable with autotools I might
give a go someday.

Cheers,
Sergio

Re: [fuse-emulator-devel] TTX2000S emulation

[Alistair <ali...@zx...>]

On 31/07/2019 22:05, Sergio Baldoví wrote:
> Umm... the basic implementation could be:
> 
> 1. Add foo_port (numeric) and foo_address (string) to settings.dat
> 2. Copy values from settings_current in ttx2000s_reset()
> 
> If you allow non-consecutive ports, then one parameter/port for each
> channel is needed. Otherwise you could calculate port+1, port+2 and port+3?
> 
> Cheers,
> Sergio
> 

Thanks, the other question is, should this be made optional to compile 
like I believe spectranet is for the targets that have no socket.c in 
compat?

Something like an #ifdef BUILD_TTX2000S around everything and stuff in 
the autotools source (configure.ac?)

Re: [fuse-emulator-devel] TTX2000S emulation

[Sergio B. <ser...@gm...>]

On 30/7/19 0:22, Alistair wrote:
> On 29/07/2019 23:02, Sergio Baldoví wrote:
>>> I've only tested on Windows, and the code still needs a way to override
>>> default settings from the fuse config, but I wasn't sure how to do that.
>>
>> If you want a tip, please explain what are you trying to achieve.
>>
> 
> I would like add the ability to override the default IP and port values
> with command arguments and config file settings but I know that involves
> machine generated code and things.

Umm... the basic implementation could be:

1. Add foo_port (numeric) and foo_address (string) to settings.dat
2. Copy values from settings_current in ttx2000s_reset()

If you allow non-consecutive ports, then one parameter/port for each
channel is needed. Otherwise you could calculate port+1, port+2 and port+3?

Cheers,
Sergio

Re: [fuse-emulator-devel] TTX2000S emulation

[Alistair <ali...@zx...>]

On 29/07/2019 23:02, Sergio Baldoví wrote:
>> I've only tested on Windows, and the code still needs a way to override
>> default settings from the fuse config, but I wasn't sure how to do that.
> 
> If you want a tip, please explain what are you trying to achieve.
> 

I would like add the ability to override the default IP and port values 
with command arguments and config file settings but I know that involves 
machine generated code and things.

Alistair

[fuse-emulator-devel] Fwd: TTX2000S emulation

[Sergio B. <ser...@gm...>]

El sáb., 27 jul. 2019 a las 12:06, Alistair escribió:
>
> Hi all, I've done some more code for the TTX2000S teletext adapter
> feature branch and made a fork and "merge request" for it
> https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/6/

Thank you. Merged with cosmetic changes.

> I don't know if sourceforge mails anyone, or if the alert just lurks on
> the website until you log in.

SF sends notifications, but are opt-in. The mailing list has a wider audience.

> I've only tested on Windows, and the code still needs a way to override
> default settings from the fuse config, but I wasn't sure how to do that.

If you want a tip, please explain what are you trying to achieve.

Cheers,
Sergio

[fuse-emulator-devel] TTX2000S emulation

[Alistair <ali...@zx...>]

Hi all, I've done some more code for the TTX2000S teletext adapter 
feature branch and made a fork and "merge request" for it 
https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/6/

I don't know if sourceforge mails anyone, or if the alert just lurks on 
the website until you log in.

I've only tested on Windows, and the code still needs a way to override 
default settings from the fuse config, but I wasn't sure how to do that.

Alistair.

Re: [fuse-emulator-devel] Formatting disks in CP/M Plus

[Gergely S. <sz...@hu...>]

On Sun, Apr 21, 2019 at 11:16:16PM +0200, Sergio Baldoví wrote:
> Hi Phil,
> 
> On 17/4/19 13:53, Phil Reynolds wrote:
> > Among the things I've been meaning to try out on Fuse over the years is
> > CP/M Plus - for the +3 of course - and I have at last reached the point
> > of trying it.
> > 
> > However, I cannot get it to format emulated disks. I call up DISCKIT
> > and follow the prompts, but, when the formatting begins, I see a 0,
> > then this message:
> > 
> > Disc error on drive A: track 0, sector #05 - check read
> > 
> > The Retry and Cancel options are offered. (same happens if drive B: is
> > used)
> > 
> > Is this expected or is there something I need to do to get this to work?
> > 
> 
> It's looks like a bug. I've filled [bug:#453]:
> https://sourceforge.net/p/fuse-emulator/bugs/453/
> 
> Thanks for reporting this issue.
> 
> Cheers,
> Sergio

Hi Phil,

I post a patch to fix this bug (https://sourceforge.net/p/fuse-emulator/bugs/453/).

Regards,
Gergely

Re: [fuse-emulator-devel] Formatting disks in CP/M Plus

[Sergio B. <ser...@gm...>]

Hi Phil,

On 17/4/19 13:53, Phil Reynolds wrote:
> Among the things I've been meaning to try out on Fuse over the years is
> CP/M Plus - for the +3 of course - and I have at last reached the point
> of trying it.
> 
> However, I cannot get it to format emulated disks. I call up DISCKIT
> and follow the prompts, but, when the formatting begins, I see a 0,
> then this message:
> 
> Disc error on drive A: track 0, sector #05 - check read
> 
> The Retry and Cancel options are offered. (same happens if drive B: is
> used)
> 
> Is this expected or is there something I need to do to get this to work?
> 

It's looks like a bug. I've filled [bug:#453]:
https://sourceforge.net/p/fuse-emulator/bugs/453/

Thanks for reporting this issue.

Cheers,
Sergio

[fuse-emulator-devel] Formatting disks in CP/M Plus

[Phil R. <phi...@ti...>]

Among the things I've been meaning to try out on Fuse over the years is
CP/M Plus - for the +3 of course - and I have at last reached the point
of trying it.

However, I cannot get it to format emulated disks. I call up DISCKIT
and follow the prompts, but, when the formatting begins, I see a 0,
then this message:

Disc error on drive A: track 0, sector #05 - check read

The Retry and Cancel options are offered. (same happens if drive B: is
used)

Is this expected or is there something I need to do to get this to work?

-- 
Phil Reynolds
mail: phi...@ti...
Web: http://phil.tinsleyviaduct.com/

Re: [fuse-emulator-devel] Fwd: small problem with fuse :)

[Sergio B. <ser...@gm...>]

Hi Krasi,

Thank you for reporting the issue. The first step to fix a problem is to
be aware that exists. I've filled a bug in Fuse's tracker:
https://sourceforge.net/p/fuse-emulator/bugs/450/

Sooner or later someone will have a look.

Cheers,
Sergio

On 4/3/19 23:52, Philip Kendall wrote:
> [ Forwarding with Krasi's permission, please keep him copied on any
> replies. Krasi, you'll need to subscribe to the list to reply to anything ]
> 
> The files in question are at least temporarily
> at https://www.dropbox.com/s/trrq5xwp73q5fr6/edskimagesnotworkinginfusel.zip?dl=0
> 
> ---------- Forwarded message ---------
> From: *Krasimir Hristov* <khr...@gm... <mailto:khr...@gm...>>
> Date: Fri, Feb 1, 2019 at 8:11 PM
> Subject: small problem with fuse :)
> To: <phi...@sh... <mailto:phi...@sh...>>
> 
> 
> Hi Philip,
> I attach few EDSK images works in emulator X (specemu, spectaculator,
> zxspin), but not Fuse. It also works if written back to a real disk, so
> I know the disk image is good." Hopefully they will be interested in
> finding out why it doesn't work in Fuse :)
> 
> I talking with Simon and He say ...
> 
> "I can understand this disk not working in fuse, as some sectors have
> extra data. Cyl 2 Sector 17 is 256 bytes, but there are 256+350 bytes
> stored. Fuse probably doesn't skip the right amount of data before
> reading the next sector."
> 
> "I've seen other programs with the same problem. The EDSK specification
> records the number of stored bytes, but some programs assume the sector
> size is the number of stored bytes. SAMdisk bends the rules, but the
> other programs have a bug. It's possible this is the bug in Fuse too."
> 
> "I think it has a problem when processing the data inside the image,
> because it doesn't understand the extensions used. When it reaches a
> point where it doesn't understand the data it will return an error. I
> think the error is reported as "failed to open", but it means "failed to
> process"."
> 
> "Fuse needs to respect the "stored data size" for EDSK sectors. That
> seems to be the main cause of these failing disk images."
> 
> Greets,
> Krasi
> 
> p.s. just work for weekend :)
> 
> 
> 
> 
> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel
> 

Re: [fuse-emulator-devel] Emulation speed control UI

[Derek F. <df...@us...>]

 > A toolbar is long overdue. If you want to try it, I'd suggest to leave
 > GTK+ 2 and first GTK+ 3 versions out and focus on GTK+ 3 API that is
 > not deprecated.

I had a go at adding a toolbar. There's a patch against a fresh clone of 
1.5.7 here:

https://sourceforge.net/p/fuse-emulator/patches/418/

I didn't know what buttons to put in it, so I put in ones which I use 
myself. Programmer's prerogative. :) Clearly a different set would be 
more suitable for the mainstream. Switching in different functions is 
easy provided the functions required are already accessible from a menu 
- the menu and toolbar callbacks in GTK use the same signature. I kept 
my selection of buttons isolated with conditional compilation so an 
alternative set should be easily switchable.

What I have looks like this:

https://sourceforge.net/p/fuse-emulator/patches/_discuss/thread/42ee430fcf/d0e4/attachment/fuse-toolbar-1.png

It only really works in 2x size and above. In 1x size either there's 
only room for a couple of buttons, or the buttons have to be so tiny 
they're unusable. Dynamic toolbar selection or resizing might be 
possible, but one step at a time.

The icons I've used came from the XFCE standard set, chosen because 
they're licenced under GPLv2 the same as fuse. Someone with more 
graphical sense than me is needed to choose icons suitable for the 
mainstream. Also, I use KDE, so I don't know how this stuff behaves 
under GNOME/GTK theming.

There might be some nuances in fuse or its code which I don't properly 
understand. The keyboard joystick seems OK. There might be other stuff 
which needs adapting.

Some notes on the code modifications required:

The keyboard handling is a tricky business. The emulated Spectrum needs 
to grab and respond to keypresses as a priority, but it appears to pass 
those keypresses through to GTK once it's done with them. Since there's 
now a UI which receives and responds to those keypresses things get 
messy. For example, when you press ENTER on the Spectrum, the Spectrum 
responds to it, but so does the toolbar which activates the default 
selected toolbar button. After a bit of messing around I decided the 
best way to deal with this was to just swallow all keypresses which 
reach the toolbar. The menus still work with function key presses and 
keyboard shortcuts, so at present there's no reason for the toolbar to 
be keyboard accessible. Hence what I currently have is a mouse-only toolbar.

The Recreated ZX Spectrum button seen in the screenshot is a toggle, and 
the speed control cluster is a spinbutton with a reset button 
underneath. You can't use the keyboard to change the speed value (due to 
the keyboard issue described above) but rolling the mouse wheel over the 
number works well. The reset button toggles the speed back to 100% with 
a single mouse click, which is handy for instant speed up or slow down. 
Better use of the GTK interface is probably possible for these sorts of 
non-standard toolbar functions. A proper GUI design is required for 
anything a bit complicated, I think.

I followed the lead of the statusbar code for the most part, but I 
decided to use GTK resources to build the icons into the C code. This 
appears to be the standard, non-deprecated way to handle application 
specific icons, although the GTK docs weren't at all clear. That meant 
building the GTK resource compiler into the fuse build. I think I got it 
right, but advice from any GTK experts would be appreciated here.

Oh, and I was a bit out of my depth with the whole automake build stuff. 
My changes compile on my Ubuntu box, but other platforms might need 
fixing. :)

[fuse-emulator-devel] Fwd: small problem with fuse :)

[Philip K. <ph...@sh...>]

[ Forwarding with Krasi's permission, please keep him copied on any
replies. Krasi, you'll need to subscribe to the list to reply to anything ]

The files in question are at least temporarily at
https://www.dropbox.com/s/trrq5xwp73q5fr6/edskimagesnotworkinginfusel.zip?dl=0

---------- Forwarded message ---------
From: Krasimir Hristov <khr...@gm...>
Date: Fri, Feb 1, 2019 at 8:11 PM
Subject: small problem with fuse :)
To: <phi...@sh...>


Hi Philip,
I attach few EDSK images works in emulator X (specemu, spectaculator,
zxspin), but not Fuse. It also works if written back to a real disk, so I
know the disk image is good." Hopefully they will be interested in finding
out why it doesn't work in Fuse :)

I talking with Simon and He say ...

"I can understand this disk not working in fuse, as some sectors have extra
data. Cyl 2 Sector 17 is 256 bytes, but there are 256+350 bytes stored.
Fuse probably doesn't skip the right amount of data before reading the next
sector."

"I've seen other programs with the same problem. The EDSK specification
records the number of stored bytes, but some programs assume the sector
size is the number of stored bytes. SAMdisk bends the rules, but the other
programs have a bug. It's possible this is the bug in Fuse too."

"I think it has a problem when processing the data inside the image,
because it doesn't understand the extensions used. When it reaches a point
where it doesn't understand the data it will return an error. I think the
error is reported as "failed to open", but it means "failed to process"."

"Fuse needs to respect the "stored data size" for EDSK sectors. That seems
to be the main cause of these failing disk images."

Greets,
Krasi

p.s. just work for weekend :)

[fuse-emulator-devel] Improving Russian clone emulations

[Alan C. <al...@ll...>]

I've been adding the NemoIDE interface emulation to the Fuse pentagon
model and after a certain amount of chasing down all the places I need to
add it I have it working kind of. At that point however I hit a fairly
fundamental problem in the core code.

The ZX-BUS interface on the systems seems to be a bit weird. If a slot
claims an I/O range then that same I/O range does not appear to be
propogated on to the other slots or the mainboard (which comes last). In
addition the ports *disappear* in TRDOS paging mode.

For the NemoIDE this is particularly problematic as the decode range is
low byte only  0x1E, 0x10 which means it tends to clash with the paging
registers and thus makes a lot of things somewhat useless.

I'll add the Scorpion's SMUC IDE as well at some point which isn't such a
problem (16bit decode 18A3 , 18A2).

Has anyone looked at the ZX-BUS and related changes ?

Alan

[fuse-emulator-devel] Improvements to save/load binary patch

[Derek F. <df...@us...>]

I use the "save binary" feature a lot and have changed its behaviour 
slightly in my local build. I've created a patch which others might find 
useful.

The main issue I had was that selecting the save option always popped 
the file selector dialog. Since I always save to the same file, 
navigating around to choose the same file over and over was 
unnecessarily time consuming. I changed the save-binary dialog code to 
store the last used filename and default straight to that next time the 
feature is used. This usage pattern adds a mouse click if the user wants 
to specify a different filename (to pop the file selector), but saves 
lots of mouse clicks if the user wants to use the same output file all 
the time.

I also store the last used start and length values so they can be 
offered as defaults, and I updated the load-binary side of the feature 
in the same way. I rarely use load-binary, but it seemed to make sense 
to ensure save and load worked the same way.

I made a couple of other clean ups - setting widget focus to remove the 
need for a tab keypress was one, left align the filename in the dialog 
so it looks sensible if resized was the other. Plus I commented the code 
as I worked out how it worked. :)

These changes are in patch 416:

https://sourceforge.net/p/fuse-emulator/patches/416/

if anyone thinks they might useful.

Re: [fuse-emulator-devel] AMX Mouse

[Sergio B. <ser...@gm...>]

Hi Alberto,

On 18/2/19 19:53, Alberto Narduzzi wrote:
> This said, I really would like to see the AMX mouse emulated in FUSE. I
> know that only a very few programs use it, specifically AMX products;
> but it would be yet another peripheral emulated.
> I have consistent idea about what it would need; I just guess we need to
> emulate the hardware, first. Is there something I can look into just to
> immerse myself in the mess of Spectrum hardware?

Emulating AMX Mouse might be a challenge. To understand how works the
peripheral, velesoft is the reference site for technical info
(schematics and port details):
https://velesoft.speccy.cz/othermouse-cz.htm

and you should have a look at Z80 PIO datasheet too.

Cheers,
Sergio

Re: [fuse-emulator-devel] AMX Mouse

[Alberto G. <be...@ig...>]

On Mon, Feb 18, 2019 at 08:53:15PM +0200, Alberto Narduzzi wrote:
> First, hello everybody.
> 
> Secondly, I know that just joining a development community and asking
> something is not so polite; but I am a developer (born thanks to the
> Spectrum, btw) since more than 30 years, so I believe I could be of some
> help, eventually.
> 
> This said, I really would like to see the AMX mouse emulated in FUSE. I
> know that only a very few programs use it, specifically AMX products; but
> it would be yet another peripheral emulated.
> I have consistent idea about what it would need; I just guess we need to
> emulate the hardware, first. Is there something I can look into just to
> immerse myself in the mess of Spectrum hardware?

Hi!

That's quite a generic question, but if you know the technical details
of how the AMX mouse works then I guess that you could start by
looking at peripherals/kempmouse.c as an example.

Then when you have some working code you could post the patches on
Fuse's ticket tracker so they can be reviewed:

   https://sourceforge.net/p/fuse-emulator/patches/

Berto

[fuse-emulator-devel] AMX Mouse

[Alberto N. <alb...@gm...>]

First, hello everybody.

Secondly, I know that just joining a development community and asking
something is not so polite; but I am a developer (born thanks to the
Spectrum, btw) since more than 30 years, so I believe I could be of some
help, eventually.

This said, I really would like to see the AMX mouse emulated in FUSE. I
know that only a very few programs use it, specifically AMX products; but
it would be yet another peripheral emulated.
I have consistent idea about what it would need; I just guess we need to
emulate the hardware, first. Is there something I can look into just to
immerse myself in the mess of Spectrum hardware?

Thank you for your kindness,
Alberto

Re: [fuse-emulator-devel] Emulation speed control UI

[Sergio B. <ser...@gm...>]

Hi Thrice,

On 6/2/19 10:31, Thrice via fuse-emulator-devel wrote:
> Hmmm, my git-fu isn't quite good enough yet. I need to look at
> publicising specific commits or patches. :o} I have the work in a
> branch, here:
> 
> https://sourceforge.net/u/thricenightly/fuse-emulator/ci/df-clickable-speed-status/tree/

Thanks for sharing. You can generate patch files for the last 4 (N?)
commits as:

    git format-patch -4 HEAD

> I think on reflection making the status bar interactive is a poor idea.
> Statusbars show status, users don't expect them to be clickable. The
> correct approach is to a add a toolbar to the GUI. I don't know how to
> do that either, since my GTK-fu is worse than my git-fu, but I'm going
> to give it a go. I'm keen to learn and make a contribution.

A toolbar is long overdue. If you want to try it, I'd suggest to leave
GTK+ 2 and first GTK+ 3 versions out and focus on GTK+ 3 API that is not
deprecated.

I think than when GTK+ 4 is released (2019?), we'll drop GTK+ 2 code and
focus on porting to GTK+ 4.

Cheers,
Sergio

Re: [fuse-emulator-devel] Emulation speed control UI

[Thrice <thr...@us...>]

On 05/02/2019 22:52, Sergio Baldoví wrote:
> Hi Thrice,
> 
> On 4/2/19 21:13, Thrice via fuse-emulator-devel wrote:
>> I've made a change to my personal fork of Fuse which I find useful.
>>
>> In the very bottom right corner of the main window statusbar there's a
>> label showing the current emulation speed. It normally sits at 100%.
>> I've modified that to make it responsive to the mouse. [...]
> Thanks for the offering. I'm not sure if it will be merged but
> definitely I'd like to test it. It's a nice touch enabling this
> functionality on the speed label. I'd suggest to point to a commit in
> your repository or add a patch ticket at SourceForge to let people
> review your code and take it if found interesting.

Hmmm, my git-fu isn't quite good enough yet. I need to look at 
publicising specific commits or patches. :o} I have the work in a 
branch, here:

https://sourceforge.net/u/thricenightly/fuse-emulator/ci/df-clickable-speed-status/tree/

which hopefully anyone can clone from? There's other stuff in there but 
all the speed control bits are at the top of the log. I acknowledge I 
need to learn to do this sort of thing better.

I think on reflection making the status bar interactive is a poor idea. 
Statusbars show status, users don't expect them to be clickable. The 
correct approach is to a add a toolbar to the GUI. I don't know how to 
do that either, since my GTK-fu is worse than my git-fu, but I'm going 
to give it a go. I'm keen to learn and make a contribution.

Re: [fuse-emulator-devel] Profiler - how is it useful?

[Sergio B. <ser...@gm...>]

Hi Thrice,

On 3/2/19 13:37, Thrice via fuse-emulator-devel wrote:
> I was looking at the profiler this morning. There's no documentation, so
> I had to start with the code and work out what it was telling me.

Right. This is a known outstanding bug:
https://sourceforge.net/p/fuse-emulator/bugs/303/

> My conclusion is that it reports the number of T-states the emulator spends
> with the PC at each address. Assuming that's correct, it rather left me
> wondering what use that might be. :)

I've used it with SkoolKit disassembly toolkit. That allows to identify
the code and the data, giving a better disassembly code to start with.

Cheers,
Sergio

Re: [fuse-emulator-devel] Emulation speed control UI

[Sergio B. <ser...@gm...>]

Hi Thrice,

On 4/2/19 21:13, Thrice via fuse-emulator-devel wrote:
> I've made a change to my personal fork of Fuse which I find useful.
> 
> In the very bottom right corner of the main window statusbar there's a
> label showing the current emulation speed. It normally sits at 100%.
> I've modified that to make it responsive to the mouse. [...]
Thanks for the offering. I'm not sure if it will be merged but
definitely I'd like to test it. It's a nice touch enabling this
functionality on the speed label. I'd suggest to point to a commit in
your repository or add a patch ticket at SourceForge to let people
review your code and take it if found interesting.

Cheers,
Sergio