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] Emulation speed control UI

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

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. If you hover the 
mouse pointer over it and turn the wheel it increases emulation speed by 
20 percentage points; likewise, it slows emulation down if the wheel is 
turned the other way. Also, double clicking on the label toggles between 
whatever value the speed is at and 100%, so if you're running at, say, 
150%, and double click that value, it immediately sets the speed to 
100%. Double click again and it goes back to 150%.

I find these changes useful for doing Spectrum development work - "speed 
it up to buzz past this bit, double click to go back to normal speed, 
now slow this bit right down, etc..." - without having to continuously 
go back to the settings dialog. Also, a quick and easy slow down feature 
reminds me of my old SlowMo device. :)

Is there any interest in having this in mainline? I could make a pull 
request if so.

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

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

> called if I know the address of the function, and the instruction there 
> takes a constant number of T-states? I can't think how to get a 
> function's run time though.

A word of warning. The contended memory banks on the ZX Spectrum have
weird and wonderful wait state patterns as do contended I/O cycles. In
some memory therefore you won't get constant numbers of T states for an
instruction

(In fact if you've got performance problems one of the first things to do
is put timing critical stuff into uncontended space)

Alan

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

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

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. 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. :)

Other profiling use cases I'm familiar with tell me how many times a 
particular function or subroutine is called within a given run, and 
maybe how long each routine takes on average. The Fuse profiler 
information might be able to tell me the number of times a function is 
called if I know the address of the function, and the instruction there 
takes a constant number of T-states? I can't think how to get a 
function's run time though.

My current Spectrum project is now taking too long somewhere in the main 
loop. I need to find out where so I know how to focus my optimisation 
efforts. I also need to be able to tell if my "improvements" are 
improving things or making them worse (it's sometimes less than obvious, 
especially to non-Z80 experts like myself). Can the Fuse profiler help 
with this? What's the technique I should be using?

Re: [fuse-emulator-devel] [fuse-emulator-cvs] [fuse] branch master updated: Check if a file is a regular file only when reading

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

On Sun, Jan 13, 2019 at 10:16:29PM +0000, sbaldovi--- via fuse-emulator-cvs wrote:

[ ... ]

>     Check if a file is a regular file only when reading

Thanks Sergio, I just found that one as well ;-)

Cheers,

Phil

Re: [fuse-emulator-devel] GTK update required for 1.5.7 - intentional?

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

On Wed, Jan 09, 2019 at 11:24:17PM +0100, Sergio Baldoví wrote:

> > Was this intentional? It wasn't mentioned in the release
> > notes. More importantly, is it desirable?
> 
> Thanks. This wasn't fully intentional, otherwise we should have
> bumped the minimum required version at configure.ac to show a proper
> error message before compiling.

I would also like to remind that Fuse can still be built with GTK+2
(using --disable-gtk3), which should not be a problem even in very old
distros.

I confirmed that this works with Fuse 1.5.7.

Berto

Re: [fuse-emulator-devel] GTK update required for 1.5.7 - intentional?

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

On 8/1/19 18:18, Thrice via fuse-emulator-devel wrote:
> 
> Was this intentional? It wasn't mentioned in the release notes. More
> importantly, is it desirable?

Thanks. This wasn't fully intentional, otherwise we should have bumped
the minimum required version at configure.ac to show a proper error
message before compiling.

Cheers,
Sergio

Re: [fuse-emulator-devel] GTK update required for 1.5.7 - intentional?

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

On Tue, Jan 08, 2019 at 11:20:14PM +0100, Alberto Garcia wrote:

> Does it work if you change the GTK_CHECK_VERSION() lines around the
> GdkSeat parts from 3.0.0 to 3.20.0 ?

I verified that updating this check is enough to fix the build, and I
managed to successfully build Fuse 1.5.7 with Ubuntu 14.04.

Here's the patch:

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

Thanks for reporting the problem!

Berto

Re: [fuse-emulator-devel] GTK update required for 1.5.7 - intentional?

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

On Tue, Jan 08, 2019 at 05:18:25PM +0000, Thrice via fuse-emulator-devel wrote:
> I tried to build the emulator v1.5.7 on an older laptop today and it failed
> with:
> 
> ui/gtk/gtkmouse.c: In function ‘ui_mouse_grab’:
> ui/gtk/gtkmouse.c:138:3: error: unknown type name ‘GdkSeat’
>    GdkSeat *seat;
> 
> The GdkSeat API is "since 3.2.0" of GTK:

You mean 3.20 I guess :-)

Does it work if you change the GTK_CHECK_VERSION() lines around the
GdkSeat parts from 3.0.0 to 3.20.0 ?

Berto

[fuse-emulator-devel] GTK update required for 1.5.7 - intentional?

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

I tried to build the emulator v1.5.7 on an older laptop today and it 
failed with:

ui/gtk/gtkmouse.c: In function ‘ui_mouse_grab’:
ui/gtk/gtkmouse.c:138:3: error: unknown type name ‘GdkSeat’
    GdkSeat *seat;

The GdkSeat API is "since 3.2.0" of GTK:

https://developer.gnome.org/gdk3/stable/GdkSeat.html

which is later than my laptop's installed version.

As an Ubuntu user I note that according to the Ubuntu releases page:

https://packages.ubuntu.com/search?keywords=libgtk-3-dev

that puts compilation of Fuse out of reach for anyone not running the 
latest release (18.04, Bionic). In particular it means anyone on Xenial 
LTS (16.04, supported until April 2021) can't build Fuse.

Was this intentional? It wasn't mentioned in the release notes. More 
importantly, is it desirable?

[fuse-emulator-devel] Fuse's 20th anniversary

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

Happy new year!

Thinking on new year's resolutions and foreseeing upcoming events, I
realise that Fuse achieves its 20th anniversary around July 2019:

https://groups.google.com/d/msg/comp.sys.sinclair/ZvlrQ_c151w/kAtGw1g4zHEJ

No presents needed but would be nice :-)

Cheers,
Sergio

Re: [fuse-emulator-devel] Small keyboard image

[Fredrick M. <fr...@sp...>]

> On 31 Dec 2018, at 16:16, Thrice via fuse-emulator-devel <fus...@li...> wrote:
> 
> My assumption was that Fred meant this file:
> 
> https://sourceforge.net/p/fuse-for-macosx/code/HEAD/tree/trunk/fuse/fusepb/resources/48k.png?format=raw
> 
> That's certainly what I'd like to see when I need keyboard help!

Yep, that’s the one!

Fred

Re: [fuse-emulator-devel] Small keyboard image

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

On Mon, Dec 31, 2018 at 04:16:22PM +0000, Thrice via fuse-emulator-devel wrote:
> My assumption was that Fred meant this file:
> 
> https://sourceforge.net/p/fuse-for-macosx/code/HEAD/tree/trunk/fuse/fusepb/resources/48k.png?format=raw
> 
> That's certainly what I'd like to see when I need keyboard help!

Nice, thank you :-)

https://sourceforge.net/p/fuse-emulator/feature-requests/138/ created.

Cheers,

Phil

Re: [fuse-emulator-devel] Small keyboard image

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

My assumption was that Fred meant this file:

https://sourceforge.net/p/fuse-for-macosx/code/HEAD/tree/trunk/fuse/fusepb/resources/48k.png?format=raw

That's certainly what I'd like to see when I need keyboard help!

On 31/12/2018 15:39, Philip Kendall wrote:
> On Sun, Dec 30, 2018 at 09:04:55PM +0000, Fredrick Meunier wrote:
>>
>> There is a suitable higher resolution keyboard image I use on the Mac if someone would like to write support to use that as the keyboard image on GTK+/Win32 etc.
> 
> The GTK+ code for showing the keyboard picture is frankly more
> complicated than it would be to show a bitmap in the first place (it
> converts lib/keyboard.scr to a bitmap before doing anything else...), so
> please give a pointer to macOS image and we'll do something with it :-)
> 
> Cheers,
> 
> Phil
> 
> 
> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel
> 

Re: [fuse-emulator-devel] Small keyboard image

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

On Sun, Dec 30, 2018 at 09:04:55PM +0000, Fredrick Meunier wrote:
> 
> There is a suitable higher resolution keyboard image I use on the Mac if someone would like to write support to use that as the keyboard image on GTK+/Win32 etc.

The GTK+ code for showing the keyboard picture is frankly more
complicated than it would be to show a bitmap in the first place (it
converts lib/keyboard.scr to a bitmap before doing anything else...), so
please give a pointer to macOS image and we'll do something with it :-)

Cheers,

Phil

Re: [fuse-emulator-devel] Small keyboard image

[Fredrick M. <fr...@sp...>]

> On 27 Dec 2018, at 13:19, Thrice via fuse-emulator-devel <fus...@li...> wrote:
> 
> Is there any reason the keyboard image which appears via "Help->Keyboard..." is such a small one? On any modern monitor some of the tiny text, particularly the red on black, is virtually illegible.

The reason is that the same image is used in 320x240 widget user interfaces that are typically full screen and also in the GTK+ and Win32 windowed screens.

There is a suitable higher resolution keyboard image I use on the Mac if someone would like to write support to use that as the keyboard image on GTK+/Win32 etc.

Fred

Re: [fuse-emulator-devel] Small keyboard image

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

On 27/12/2018 13:19, Thrice via fuse-emulator-devel wrote:
> Wouldn't a bigger graphic image, or a photo, be better? It'd certainly 
> work better for me!

A vector graphic would be good, with the window scalable to suit any 
monitor.

[fuse-emulator-devel] Small keyboard image

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

Is there any reason the keyboard image which appears via 
"Help->Keyboard..." is such a small one? On any modern monitor some of 
the tiny text, particularly the red on black, is virtually illegible.

Wouldn't a bigger graphic image, or a photo, be better? It'd certainly 
work better for me!

Re: [fuse-emulator-devel] recommended packages for Ubuntu 18

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

Hi Tomáš,

On 23/12/18 17:21, Tomáš Franke wrote:
> Hello
> 
> Which packages are required/recommended to apt-get install, when I want
> to build Fuse from scratch at Ubuntu 18?

Although Berto's method (apt-get build-dep) is preferred as it will be
compatible with future versions of Ubuntu, I use this direct command:

apt-get install autoconf automake m4 make libtool pkg-config flex bison
binutils gcc g++ perl groff libgtk-3-dev libsdl1.2-dev zlib1g-dev
libpng-dev libbz2-dev libxml2-dev libasound2-dev libglib2.0-dev
libaudiofile-dev libgcrypt20-dev libjpeg-turbo8-dev

You can also use the flatpak package distribution
(https://flatpak.org/setup/Ubuntu/) to get an up to date version of Fuse
without compiling:

flatpak install flathub net.sf.fuse_emulator
flatpak run net.sf.fuse_emulator

Cheers,
Sergio

Re: [fuse-emulator-devel] recommended packages for Ubuntu 18

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

On Sun, Dec 23, 2018 at 05:21:45PM +0100, Tomáš Franke wrote:

> Which packages are required/recommended to apt-get install, when I
> want to build Fuse from scratch at Ubuntu 18?

Hey,

Fuse is already included in Ubuntu, so you can install it directly
with apt-get:

   $ apt-get install fuse-emulator-gtk   (for the GTK version)
   $ apt-get install fuse-emulator-sdl   (for the SDL version)

If you still want to build Fuse yourself from scratch, you can install
all required packages with this command:

   $ apt-get build-dep fuse-emulator

For this to work you'll need to have the deb-src entries for Ubuntu 18 in
/etc/apt/sources.list

For reference, here's a list of the packages installed with that
command:

   https://packages.ubuntu.com/source/cosmic/fuse-emulator

Berto

[fuse-emulator-devel] recommended packages for Ubuntu 18

[Tomáš F. <to...@vo...>]

Hello

Which packages are required/recommended to apt-get install, when I want 
to build Fuse from scratch at Ubuntu 18?

Omikron

[fuse-emulator-devel] Fuse 1.5.7 released

[Fredrick M. <fr...@sp...>]

A new release of Fuse, the Free Unix Spectrum Emulator, is now available at the SourceForge project:

https://sourceforge.net/projects/fuse-emulator/

Highlights of this release include:
GTK+ 3: Make the offset entry wider in memory browser
GTK+: Remove duplicated surface creation code
GTK+: Remove use of deprecated gtk_device_(un)grab functions
GTK+/Win32: Add *.bin as an allowed filetype to file selectors and amend .fmf filetype
Improve Fuse's Kempston mouse handling under GTK+ 3.x
"Save binary" command can now save 65536 bytes again (regression introduced in 1.5.6)
Various minor bugfixes
Many thanks to everyone who's contributed to this release. Source code and binaries for Windows are currenly available on the SourceForge site; compiled binaries for various other platforms should become available in the next few days.

Fred

Re: [fuse-emulator-devel] Fuse 1.5.7 Release

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

Hi Fred,

On 9/12/18 13:15, Fredrick Meunier wrote:
> Hi all,
> I've prepared the proposed release tarball of fuse 1.5.7[1] and uploaded it to sourceforge in a staging directory. The tar file can be found in https://www.dropbox.com/sh/135l1re550gsxix/AABGSOKDGrBDjLzbK_kUXLAMa?dl=0 [2] in the meantime for your final chance to flag showstoppers.
> 
> I’d appreciate it if matching Win32 binaries could be built to add to the release directories as that seems to be the key platform downloading from sourceforge.

Thanks. These are the Windows binaries...

Fuse 1.5.7 (Windows installer)
https://www.dropbox.com/s/prnf9w2p1jsvku0/fuse-1.5.7-win32-setup.exe?dl=1

Fuse 1.5.7 (Windows ZIP)
https://www.dropbox.com/s/qf02yjdgzn0xpy2/fuse-1.5.7-win32.zip?dl=1

SHA1 checksums:
2a8d5837b73df4cb3493f176d3ad297be081e2f2 *fuse-1.5.7-win32-setup.exe
5f6f4bfa95ffb0d5119e7ad5856bfc72f0082f31 *fuse-1.5.7-win32.zip

Cheers,
Sergio

Re: [fuse-emulator-devel] Fuse 1.5.7 Release

[Fredrick M. <fr...@sp...>]

> On 11 Dec 2018, at 08:19, Philip Kendall <ph...@sh...> wrote:
> 
>> As previously noted, we’d aim to release any bug fixes or new features in the next release in about 1 month which at the moment points to the weekend of the 8th of September.
> 
> Probably not quite then ;-)

:) I need to automate this email! Let’s try for the weekend of the 26th of January instead. 

> For what it's worth, my real life work is currently taking up far too
> much of my time so I'm not having much (any...) time for Fuse. I keep
> receiving assurances that things will be better in the New Year when I
> hope to smooth off the rough edges on the GTK+ arbitrary scaling patch.

I can relate! The time I’ve had I’ve been trying to streamline the release process though there is plenty more to do there. 

Fred

Re: [fuse-emulator-devel] Fuse 1.5.7 Release

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

On Sun, Dec 09, 2018 at 11:15:49PM +1100, Fredrick Meunier wrote:
> Hi all,
> I've prepared the proposed release tarball of fuse 1.5.7[1] and uploaded it to sourceforge in a staging directory. The tar file can be found in https://www.dropbox.com/sh/135l1re550gsxix/AABGSOKDGrBDjLzbK_kUXLAMa?dl=0 [2] in the meantime for your final chance to flag showstoppers.
> 
> I’d appreciate it if matching Win32 binaries could be built to add to the release directories as that seems to be the key platform downloading from sourceforge.
> 
> Phil: when you have a chance, it would be great if you could generate a signature for the release binary and add it to the staging directory.

Done. Due to incompetence, I accidently uploaded a "new" copy of
fuse-1.5.7.tar.gz. I don't see why this will cause a problem.

> As previously noted, we’d aim to release any bug fixes or new features in the next release in about 1 month which at the moment points to the weekend of the 8th of September.

Probably not quite then ;-)

For what it's worth, my real life work is currently taking up far too
much of my time so I'm not having much (any...) time for Fuse. I keep
receiving assurances that things will be better in the New Year when I
hope to smooth off the rough edges on the GTK+ arbitrary scaling patch.

Cheers,

Phil

[fuse-emulator-devel] Fuse 1.5.7 Release

[Fredrick M. <fr...@sp...>]

Hi all,
I've prepared the proposed release tarball of fuse 1.5.7[1] and uploaded it to sourceforge in a staging directory. The tar file can be found in https://www.dropbox.com/sh/135l1re550gsxix/AABGSOKDGrBDjLzbK_kUXLAMa?dl=0 [2] in the meantime for your final chance to flag showstoppers.

I’d appreciate it if matching Win32 binaries could be built to add to the release directories as that seems to be the key platform downloading from sourceforge.

Phil: when you have a chance, it would be great if you could generate a signature for the release binary and add it to the staging directory.

As previously noted, we’d aim to release any bug fixes or new features in the next release in about 1 month which at the moment points to the weekend of the 8th of September.

Thanks,
Fred

[1] commit 8c05bfdbafed9013f799bf16137e9c9983573d4a
[2] sha1sum:
53ffc684d4b1054a2e4ef1c36de456ab170d5030  fuse-1.5.6.tar.gz