Re: Hotlist window issue

2023-08-27 Thread Christian Ludlam

> On 27 Aug 2023, at 22:42, Harriet Bazley  wrote:
> 
> On 27 Aug 2023 as I do recall,
>  Frederick Bambrough  wrote:
> 
>> Is this a known bug?
>> 
>> Hotlist ignores 'Allow windows off screen' configuration settings when
>> 'off screen' is disallowed. It moves freely off screen in all directions
>> except 'top' where it stops with the top edge of the title bar off screen.
>> 
>> Other NetSurf windows do as expected.
>> 
> I reported an offscreen-hotlist-related window issue back in 2021.  It
> has never been acknowledged, let alone confirmed or resolved (and it's
> still present, and as annoying as ever).
> https://bugs.netsurf-browser.org/mantis/view.php?id=2831
> 
> Its is not normal RISC OS behaviour for the 'toggle window size' icon to
> expand the window *beyond the edge of the screen*, whatever the 'Allow
> windows off screen' configuration is, and indeed other NetSurf windows
> behave as expected - you can drag them manually so that portions are
> off-screen, but as soon as you toggle the size they expand to the
> largest possible size that will fit on the screen (moving to the top of
> the screen if necessary in order to fit in the maxmimum-size window) but
> no larger.
> 
> The hotlist simply expands downwards from its current position, which
> causes the resize icon and bottom scroll arrow to disappear off the
> bottom of the screen, which under RISC OS means that you *can't* then
> resize it manually to make the bottom items accessible again….
> 

I think both problems are controlled by bit 6 of the window flags - if you
have a template editor you may be able to fix this.

Christian

___
netsurf-users mailing list -- netsurf-users@netsurf-browser.org
To unsubscribe send an email to netsurf-users-le...@netsurf-browser.org


Re: 'Base stylesheet failed to load' error

2011-11-11 Thread Christian Ludlam
On 19 Jan 2038, at 03:14, george  wrote:

> The HD on my Iyo has just been changed, and it would appear that 
> (almost) everything has copied across ok, apart from the fact that, 
> although NetSurf will load initially and display my home page when I 
> click on it the first time, subsequent attempts to access web pages 
> produces the error message in the Subject line above. Reverting to 
> version 2.8 did not cure the problem, nor did reloading the !Boot and 
> !System modules from my NAS.
> 
> Any suggestions?

I had this problem intermittently - I found the cause this morning, in fact - 
It's because 
your computer thinks it's 2038!

-- 
Christian Ludlam
christ...@recoil.org




Re: NetSurf printing

2008-02-28 Thread Christian Ludlam


On 28 Feb 2008, at 15:51, John-Mark Bell wrote:

On Thu, 28 Feb 2008 10:57:32 GMT, Dr Peter Young  
<[EMAIL PROTECTED]>

wrote:

Is there any prospect of this PostScript problem being sorted out?


Not be me at least -- it was bad enough fixing PDriverDP without  
direct
access to either a printer or, perhaps more usefully, a RISC OS  
machine. I

don't have time to wade through the thousands of pages of PostScript
language specification to work out what's required. This effort  
would be
most certainly wasted, anyway, as people who are already experts in  
dealing

with PostScript are working on improving PostScript printing.


There might be something you can do in NetSurf to get PostScript  
printing

working - Kevin Bracey had a couple of suggestions when I was adding
Unicode support to ZapRedraw:

  Yes, it's mapping the stuff to PostScript fonts that's the problem.  
Lots of
  work from a PostScript guru needed there. It might require  
PostScript 3 to

  make it work.

  

  I think we're talking at cross-purposes here. You said UCS support  
in VDU
  mode, so I assumed you meant using the system font, which can be  
achieved

  using the Service_International call to redefine character  as UCS
  character .

  Browse could do this - it sort of used characters 80-FF of the  
system font
  as a cache of recently needed characters, which it fetched on  
demand using
  Service_International during its redraw loop. It then restored them  
to their
  original definition at the end of the redraw. This worked rather  
well with
  PostScript printing - the PostScript printer driver does a very  
intelligent
  job of handling system font and its redefinition. It doesn't yet  
support

  UTF8. Still.

Makes an amusing technical challenge, I reckon, so ZapRedraw does the
same thing when plotting in the system font. I think Browse would
reprogram the system font size too (using VDU 23,17,7 or whatever).  
Good stuff.


--
Christian Ludlam
[EMAIL PROTECTED]