A couple of new problems using latest builds (now i'm testing latest #980 revision)
- Open Google and in searchbar try to paste somethings from an empty clipboard, here i got this error message:
Quote:
assertion "string && from && to && result" failed: file "utils/utf8.c", line 262
Then the machine will freeze
- ClickToFront commodity does not work anymore with Netsurf ? It's strange but on my system all programs still working fine with the commodity but once i try to "front up" a NetSurf's window nothing happen .. pls can you check ?
A couple of new problems using latest builds (now i'm testing latest #980 revision)
- Open Google and in searchbar try to paste somethings from an empty clipboard, here i got this error message:
Quote:
assertion "string && from && to && result" failed: file "utils/utf8.c", line 262
That's a core problem - bugtracker please!
Quote:
- ClickToFront commodity does not work anymore with Netsurf ? It's strange but on my system all programs still working fine with the commodity but once i try to "front up" a NetSurf's window nothing happen .. pls can you check ?
It's a standard window.class window that hasn't changed in years. Even if it doesn't work (can't check at the moment) I have no idea how I'd fix it. You're not trying to bring it in front of an "always on top" window are you?
in many of the builds lately i'm seeing very odd font spacing, particularly quite a lot of spacing inserted before any special characters, like parentheses or brackets or apostrophes. i've run fixfonts a bunch of times, just to make sure that wasn't it.
is this just me? are others seeing this? my test system is AOS 4.1u6 with all of the latest updates as provided by amiupdate. the hardware is a pegasos2 board with a radeon 9000 pro graphics card.
-- eliyahu
"Physical reality is consistent with universal laws. When the laws do not operate, there is no reality. All of this is unreal."
It's a standard window.class window that hasn't changed in years. Even if it doesn't work (can't check at the moment) I have no idea how I'd fix it. You're not trying to bring it in front of an "always on top" window are you?
Mmm i don't think so, ClickToFront still working fine on any window of my system, only with NetSurf it doesn't seems to work anymore, don't know why, maybe it might be related to the latest ClickToFront updates ..
ClickToFront is working here, as is the font selector (showing size 0 is normal, the sizes there are irrelevant - I did put in a request to add an option to remove the size from that gadget, and from the ASL requester, but predictably it hasn't been added)
The weird spacing is probably due to some changes in picking line breaks. I've not seen the huge spaces myself, but I suspect you have the DPI set incorrectly (prefs, rendering tab - should be set to the vertical resolution of your screenmode divided by the physical screen height in inches)
I can confirm. The NetSurf window is the only program window that does not come to front when double-clicked. I doubt this is a general window.class problem, as other ReAction-based programs behave normally.
I run Update 6 with the latest ClickToFront obtained via AmiUpdate.
OK, fixed. It was working on its own screen, but not on WB. It was errorneously not telling Intuition it was a visitor window, although why that would stop ClickToFront working is a mystery.
trixie wrote: Out of curiosity - what kind of setting is for that? The WA_PubScreen tag?
Yes. I was using WA_CustomScreen from back when it only opened a custom non-public screen. WA_PubScreen is what you're supposed to use for public screens, which also declares that the window is a visitor window.
I have no idea what difference there is between the two beyond that, nor do I know what the significance is to telling Intuition you're a visitor window.
The AutoDoc does goes to pains in the notes though to say when using public screens you must declare yourself as a visitor window, unless you're a requester, when you should absolutely not say you're a visitor window, as there's no guarantee you'll end up on the same screen.
Any fonts will do The default ones work well enough, NetSurf doesn't recognise named fonts (yet) so installing loads of fonts for web pages is pointless. The important thing is to make sure the DPI is set correctly on the rendering tab, otherwise you'll get really small text on amigans.net and other places.
Perhaps we should have a straw poll of what DPI monitors people are using, so I can set the default to something more sensible than Commodore's suggested 72 dpi?
I don't know exactly how to reproduce it but from time to time i have a crash that point at clipboard.device
I'm currently using NetSurf 3.0 Revision 1012
Quote:
Crash log for task "NetSurf" Generated by GrimReaper 53.5 Crash occured in module clipboard.device at address 0x6E6FCDF8 Type of crash: DSI (Data Storage Interrupt) exception
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
