On 5 Jan 2013, Luke Evans <luke@eversosoft.com> wrote:
> I've just installed RPCEmu on Mountain Lion - originally off the ROOL
> USB drive (0.8.8), then the 0.8.9 build from the web.
>
> There seem to be a few issues however:
> 1. The mouse seems to get messed up after leaving the RPCEmu window
> for the first time. When returning to the window, the position of the
> RISCOS mouse will get clamped to a particular boundary and not move
> beyond that - perhaps affording some movement in a portion of the
> RISCOS desktop, but not all.
I know nothing about Mac but, on a Windows installation, that problem
occurs if Settings > Mouse is set to 'Capture'. Changing to 'Follow host
mouse' fixed the problem, here.
Tony
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Saturday, 5 January 2013
Re: [Rpcemu] Issues with 0.8.9 on Mac (Mountain Lion)
I have similar issues on my single screen Mac Book Air running Lion, so I wouldn't have thought it was anything to do with the dual screens.
On 5 Jan 2013, at 06:35, Luke Evans wrote:
> Actually, further to (1) it appears that if the RPCEmu window is positioned near the origin of the main screen (bottom left) then the mouse behaves correctly when re-entering the window (transitioning from the Mac OS X desktop to the RISCOS desktop in RPCEmu). So, I think that does support the hypothesis that the issue is some offset calculation.
>
> I don't know if this is significant, but the two monitors that I have attached to my Mac Pro have slightly different geometries (the main monitor being higher resolution). Mac OS X allows you to position the logical geometry of the two screens adjacent to each other (to the left or right) with an arbitrary vertical offset of a smaller screen against a larger one. I'll need further play-time to determine if this, or simply the dual screen setup, is a factor.
>
>
> On 2013-01-04, at 7:28 PM, Luke Evans <luke@eversosoft.com> wrote:
>
>> I've just installed RPCEmu on Mountain Lion - originally off the ROOL USB drive (0.8.8), then the 0.8.9 build from the web.
>> There seem to be a few issues however:
>> 1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
>> This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
>
>
> _______________________________________________
> Rpcemu mailing list
> Rpcemu@riscos.info
> http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
On 5 Jan 2013, at 06:35, Luke Evans wrote:
> Actually, further to (1) it appears that if the RPCEmu window is positioned near the origin of the main screen (bottom left) then the mouse behaves correctly when re-entering the window (transitioning from the Mac OS X desktop to the RISCOS desktop in RPCEmu). So, I think that does support the hypothesis that the issue is some offset calculation.
>
> I don't know if this is significant, but the two monitors that I have attached to my Mac Pro have slightly different geometries (the main monitor being higher resolution). Mac OS X allows you to position the logical geometry of the two screens adjacent to each other (to the left or right) with an arbitrary vertical offset of a smaller screen against a larger one. I'll need further play-time to determine if this, or simply the dual screen setup, is a factor.
>
>
> On 2013-01-04, at 7:28 PM, Luke Evans <luke@eversosoft.com> wrote:
>
>> I've just installed RPCEmu on Mountain Lion - originally off the ROOL USB drive (0.8.8), then the 0.8.9 build from the web.
>> There seem to be a few issues however:
>> 1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
>> This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
>
>
> _______________________________________________
> Rpcemu mailing list
> Rpcemu@riscos.info
> http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Friday, 4 January 2013
Re: [Rpcemu] Issues with 0.8.9 on Mac (Mountain Lion)
…and some more detail on my point (3).
Only the top-left quarter of the RISCOS screen is drawn, suggesting that some kind of resolution doubling is confusing RPCEmu screen drawing code.
You can also see that the RISCOS screen is drawn halfway down the window's titlebar too.
Image attached (hopefully).
On my point (2), the networking, I think I may not have had the external NAT set up properly. I'll do some more experiments. Clearly the behaviour of RPCEmu isn't great under these circumstances (empty dialog window and process lock up), but that's understandable for an alpha.
-- Luke
On 2013-01-04, at 7:28 PM, Luke Evans <luke@eversosoft.com> wrote:
3. RPCEmu doesn't seem to render properly on a retina display Mac Book Pro. The RISCOS desktop renders fine on my Mac Pro, but on my Mac Book Pro, only a small portion of the window is drawn (and not correctly either). Perhaps the method to map the RISCOS screen buffer to the Mac OS X window isn't working with the very high resolution?
Re: [Rpcemu] Issues with 0.8.9 on Mac (Mountain Lion)
Actually, further to (1) it appears that if the RPCEmu window is positioned near the origin of the main screen (bottom left) then the mouse behaves correctly when re-entering the window (transitioning from the Mac OS X desktop to the RISCOS desktop in RPCEmu). So, I think that does support the hypothesis that the issue is some offset calculation.
I don't know if this is significant, but the two monitors that I have attached to my Mac Pro have slightly different geometries (the main monitor being higher resolution). Mac OS X allows you to position the logical geometry of the two screens adjacent to each other (to the left or right) with an arbitrary vertical offset of a smaller screen against a larger one. I'll need further play-time to determine if this, or simply the dual screen setup, is a factor.
On 2013-01-04, at 7:28 PM, Luke Evans <luke@eversosoft.com> wrote:
> I've just installed RPCEmu on Mountain Lion - originally off the ROOL USB drive (0.8.8), then the 0.8.9 build from the web.
> There seem to be a few issues however:
> 1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
> This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
I don't know if this is significant, but the two monitors that I have attached to my Mac Pro have slightly different geometries (the main monitor being higher resolution). Mac OS X allows you to position the logical geometry of the two screens adjacent to each other (to the left or right) with an arbitrary vertical offset of a smaller screen against a larger one. I'll need further play-time to determine if this, or simply the dual screen setup, is a factor.
On 2013-01-04, at 7:28 PM, Luke Evans <luke@eversosoft.com> wrote:
> I've just installed RPCEmu on Mountain Lion - originally off the ROOL USB drive (0.8.8), then the 0.8.9 build from the web.
> There seem to be a few issues however:
> 1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
> This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Issues with 0.8.9 on Mac (Mountain Lion)
I've just installed RPCEmu on Mountain Lion - originally off the ROOL USB drive (0.8.8), then the 0.8.9 build from the web.
There seem to be a few issues however:
1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
2. The IP tunnelling option seems to cause RPCEmu to lock up when the "Reset RISC PC" dialog is accepted. A blank alert window pops up. The main window eventually closes, but the blank alert window never seems to render properly or go away and its button does nothing. The process is effectively hung and needs killing. If you cancel the "Reset RISC PC" dialog, the IP tunnelling option remains ON in the preferences, but stopping and restarting RPCEmu has it return to the OFF state (so it probably wasn't ever set to "On", despite the state of the setting).
3. RPCEmu doesn't seem to render properly on a retina display Mac Book Pro. The RISCOS desktop renders fine on my Mac Pro, but on my Mac Book Pro, only a small portion of the window is drawn (and not correctly either). Perhaps the method to map the RISCOS screen buffer to the Mac OS X window isn't working with the very high resolution?
While I can't use RPCEmu practically yet, I'm really pleased to see this project making progress and that there's Mac support. Hopefully these issues can be addressed soon. Thanks!
-- Luke
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
There seem to be a few issues however:
1. The mouse seems to get messed up after leaving the RPCEmu window for the first time. When returning to the window, the position of the RISCOS mouse will get clamped to a particular boundary and not move beyond that - perhaps affording some movement in a portion of the RISCOS desktop, but not all.
This seems to be an incorrect bounds/offset calculation when the mouse reenters the window. I wonder if this has to do with multiple monitors (which I have), but I haven't tried on a single monitor system yet. This bad state seems to get reset if the RPCEmu window is deactivated and reactivated (i.e. click on another window, then click back on the RPCEmu window's title bar), but the situation will arise again once the mouse leaves the window bounds again.
2. The IP tunnelling option seems to cause RPCEmu to lock up when the "Reset RISC PC" dialog is accepted. A blank alert window pops up. The main window eventually closes, but the blank alert window never seems to render properly or go away and its button does nothing. The process is effectively hung and needs killing. If you cancel the "Reset RISC PC" dialog, the IP tunnelling option remains ON in the preferences, but stopping and restarting RPCEmu has it return to the OFF state (so it probably wasn't ever set to "On", despite the state of the setting).
3. RPCEmu doesn't seem to render properly on a retina display Mac Book Pro. The RISCOS desktop renders fine on my Mac Pro, but on my Mac Book Pro, only a small portion of the window is drawn (and not correctly either). Perhaps the method to map the RISCOS screen buffer to the Mac OS X window isn't working with the very high resolution?
While I can't use RPCEmu practically yet, I'm really pleased to see this project making progress and that there's Mac support. Hopefully these issues can be addressed soon. Thanks!
-- Luke
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
[Rpcemu] Risc OS 6.20
Has anyone managed to get Risc OS 6.20 running on RPCemu 0.8.9?
The install keep crashing when installing the softload ROMs. When I manually moved them across, it crashed while booting (this is from a hard drive image, not HostFS).
BTW, I'm using a Mac OS 10.7.5 host.
Cheers,
Gerald.
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
The install keep crashing when installing the softload ROMs. When I manually moved them across, it crashed while booting (this is from a hard drive image, not HostFS).
BTW, I'm using a Mac OS 10.7.5 host.
Cheers,
Gerald.
_______________________________________________
Rpcemu mailing list
Rpcemu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
Tuesday, 1 January 2013
Re: Hotlist on RISCOS
In article <5306d264c4dave@triffid.co.uk>,
Dave Symes <dave@triffid.co.uk> wrote:
> And you'll be lucky if you hit the spot (Once in a blue moon). The
> receptive bit for the D&D must be about one or two pixels in size, and
> don't ever bother if the Directory is at the bottom of the window,
> you'll never get it in.
It would make a lot of sense if a directory could be clicked on to
activate it (open directory icon) so that it could be filled. Adding to an
empty directory is indeed chancey.
--
Richard Torrens.
http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats
and more!
Dave Symes <dave@triffid.co.uk> wrote:
> And you'll be lucky if you hit the spot (Once in a blue moon). The
> receptive bit for the D&D must be about one or two pixels in size, and
> don't ever bother if the Directory is at the bottom of the window,
> you'll never get it in.
It would make a lot of sense if a directory could be clicked on to
activate it (open directory icon) so that it could be filled. Adding to an
empty directory is indeed chancey.
--
Richard Torrens.
http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats
and more!
Subscribe to:
Posts (Atom)