I didn´t know if someone still mention it:

IF you click on the URL-Line and type an url, the first char will be eaten after the second char is typed, thats really annoying.

_________________
I´m back in 2023 on Classic Amiga with my A1200/Blizzard1230IB@50Mhz, 32MB RAM, AmigaOS3.2 and ROMs, Indivision AGA MK3, Author of Amiga-Flipclock (OS4)

@1Mouse

Google+ works just fine on MorphOS. Can't tell if it didn't work in 1.9, but it doesn't matter a lot.

An

@djrikki

Quote:

Fed up having to type wwww everytime to reach a webpage lol

What do you mean?

@fingus

If the history popup really takes that long and leads to eaten chars, you can always disable it in settings.

New version of Cinnamon Writer asked to add one font file into Fonts. (I think just copying it there was a mistake.) Ever since MUIOWB initializes fonts every time I start it. This didn't happen before trying to add new fonts into Fonts. I even deleted that one font file from Fonts to put Fonts dir into the same state it was earlier but that didn't change anything. MUIOWB keeps initializing fonts (that one process taking a lot of time) everytime.

I'm wondering what might have went wrong and how to fix that ?

_________________
Rock lobster bit me. My Workbench has always preferences. X1000 + AmigaOS4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." -Seymour Cray

@Fab @Fingus

Yes - I've had to disable the history popup. It seems to eat the first character I type. This has been mentioned by others in this thread already.

@1Mouse Quote:

there are sites people can get on with other browsers that you can't reach with MUI-OWB? If so, Google+ is one of them, can reach via OWB 3.32 but not MUI-OWB

Google+ works fine here on MUI-OWB (OS4).

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@Tomppeli

By any chance, using FFS without long name enabled for your system partition? If so, the cache filename would be too long (>31 chars or so) and thus truncated, which would cause a constant reindexation by fontconfig. In MorphOS, i shortened the fontconfig cache filename to fit in less than 31 chars to avoid that kind of trouble for the FFS fans. :)

Apart from that, it could be an issue with the file dates if one the fonts has a date posterior to the cache file. This could happen if the cinnamon font has a date in the future, for instance.

Last edited by Fab on 06-Oct-2011 at 02:48 PM.

@ChrisH

Just tried again and still can't get onto Google+ it states that my Browser is no longer supported

_________________
1 AmigaOne G4XE (OS4 Pre-Release Update4)
Minimig
Sam440ep + OS4.1FE
Sam460cr + OS4.1FE

@1Mouse

Then spoof it.

@1Mouse

Just spoofed using chrome option, works fine here.

Cheers

_________________
If your nose runs and your feet smell, you're upside down.

@TiredofLife

Works here too

@Fab/Tomppeli

Same here, after adding that specific font MUI-OWB it keeps re-initializing the font cache. Filesystem used here is SFS/0, the date of the font file #?.ttf is 03-Jan-2001 and the file name of the generated cache file in the MUI-OWB's /conf/font directory is

076632dfc0747cebd47d96470394e408-ppc-amigaos.cache-2.NEW

...which seems to be the error. The old cache file is still there (without the .NEW ending). After deleting the old cache file and stripping of the .NEW from the new cache file MUI-OWB starts normal without rebuilding the cache. So there seems to be a problem with writing, renaming, deleting the old/new cache files.

Last edited by cha05e90 on 06-Oct-2011 at 08:27 PM.

_________________
X1000|II/G4|440ep|2000/060|2000/040|1000

@cha05e90

Bug report filed.

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS
Praise seitan.

@cha05e90

SFS0 here too. Removed two other cache files and renamed the one with .NEW ending removing that .NEW from the name and it won't try to initialize fonts everytime any more. Thanks !

@Thematic
Quote:

Bug report filed.

Thanks !

Last edited by Tomppeli on 07-Oct-2011 at 12:07 AM.

_________________
Rock lobster bit me. My Workbench has always preferences. X1000 + AmigaOS4.1 FE
"Anyone can build a fast CPU. The trick is to build a fast system." -Seymour Cray

@kas1e

Quote:

@daveyw Quote: Yes, that, and the "crashing almost everytime I try to download something" thing.. If you can reproduce the problem, write bug-report on the mui-owb bug-tracker. Only bugs which are reported on the bug-tracker have a luck to be fixed.

Unfortunately, I'm not too technical, so I don't know how to generate a crash log. I see you've logged a few errors with downloading files, however you were able to recover from them. For me, it's a lock-up requiring a reset. You've also mentioned specific file-types (wmv), for me its anything - lha, jpg, etc.

I think it may be caused by the fact I'm running MUI-OWB on its own screen. The file requestor appears on Workbench. Sometimes, that screen will jump to the front, other times not. And usually after downloading three or four files then the requestor doesn't appear and its crash-time.

I'm now running MUI-OWB on WB, will see how it goes.

_________________
---------------
AmigaOne X5000 P5020 2Ghz, OS 4.1
AmigaOne XE G4 800mhz, OS 4.1
A1200T 40Mhz 68040, OS 3.9

@daveyw

MUIOWB seems to be running a bit faster under Update 4. It's a bit hard to tell, I've exceeded my bandwidth for the month so I'm surfing at a reduced speed, but the interface seems snappier. Must be those MUI updates.

_________________
---------------
AmigaOne X5000 P5020 2Ghz, OS 4.1
AmigaOne XE G4 800mhz, OS 4.1
A1200T 40Mhz 68040, OS 3.9

@daveyw

Could also be updated Roadshow plus updated Picasso96ApI.library plus working SWAP.


Quote:

daveyw wrote: @daveyw MUIOWB seems to be running a bit faster under Update 4. It's a bit hard to tell, I've exceeded my bandwidth for the month so I'm surfing at a reduced speed, but the interface seems snappier. Must be those MUI updates.

_________________
Sam460ex : Radeon Rx550 Single slot Video Card : SIL3112 SATA card

@fingus

Quote:

IF you click on the URL-Line and type an url, the first char will be eaten after the second char is typed, thats really annoyi

This is because you type the second char as the history window is just opening. And since our machines are slow the history windows take a little time to open, prepare and give back focus to the URL string. You can see the OWB window go inactive briefely.

The solution is to wait half a second after typing the first char before you continue. Then you won't loose the char. Ideally the history window should openen in inactive mode, but since it's all controlled by MUI I don't think that particular popup can be told to open inactively.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Deniil715

Quote:

Ideally the history window should openen in inactive mode, but since it's all controlled by MUI I don't think that particular popup can be told to open inactively.

If that's the case has a bug been reported to Thore?

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

Has it already been reported that in OS4 verion of MUI OWB, you can't type in greek (and I suspect other non-english languages) in search engines or in forums etc?
I don't think that this has anything to do with MUI itself though.

@vulture
Yes, i know that problem (you can't also type in russian and so on). For now i do not know what problem is it, but for sure it something which should be fixed / checked.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites