Enhancer Bug thread

@kas1e
Wooah, give me chance, I've only just seen this.

@amigakit
I've PM'd you as it's easier from here.

@Raziel

1. It's not supposed to save. Read the doc for alist of actual saveable settings.

2. The word wrap as you type behaviour is derrived from the texteditor.gadget and not implemented at application level. IT's very simplistic and does not attempt to do word boundaries or rearrange and subsequent text.

Late yesterday, I opened the Multiviewer about window and got a crash. I thought the workaround for the Infowindow problem was to add an image in 'GUI Preferences/Gadgets/General/Background Texture'. I have a pattern image set in the 'Background Texture' but still get the crash. Am I confused about this or has something else gone wrong with my system?

@xenic

Is it a crash, or a freeze? Do other Enhancer programs trigger the problem when you open their About window?

@trixie

Thank you, sir

@broadblues

1. Then please take it as a festure request to make word wrapping default, or at least let the user decide if it's enabled by default.

2. Ok, so this texteditor.gadget is A-Eon aswell?
If so, could those features for word wrapping be implemented?

Or is 1. disabled by default because of 2. isn't very mature?

@Raziel

Quote:

Noted, but not going to do it till the gadget works better.

Quote:

It's this system gadget, the same on as used by NotePad, MultiEdit is essentially NotePad with all the bells and whistles added. I don't think you can access the word wrap feature from NotePad (this is distinct from the line wrapping in the display, which keeps the lines intact but wraps them in the view) so I guess it was never stress tested. BZ has been raised IIRC.

Quote:

Sort of.

@trixie
Quote:
It's actually a system freeze (with slight delay). If I'm quick enough, I can perform a warm reboot after the blank window opens but before the freeze takes hold. After the warm reboot I can recover debug output from memory that includes Grim Reaper output. The stack trace always ends in window.class. I don't think DiskImageGUI is using Infowindow but it has the same system freeze and the stack trace ends in window.class.

The other Enhancer programs trigger the same freeze when their About windows are open. I could have sworn I fixed the problem by adding a pattern image in 'GUI Preferences/Gadgets/General/Background Texture'. Is adding an image in 'Background Texture' supposed to work around the problem or am I getting things confused?

@xenic

That *is* suposed to be the work arround yes, check your UI prefs maybe you reset them without realising?

Can Multiviewer please support the PageUp/Down keys? Thanks.

@daveyw

IT uses them to page through the filelist.

@broadblues
Quote:
I checked and my setting which is:
Sys:Prefs/Presets/Default/Common/Patterns/smallerw.png

It's the same setting that is there when I booted from the OS4.1FE CD. I cold booted with the OS4.1FE CD and because there is no infowindow.class on that CD, I tested DiskimageGUI (which has the same problem as infowindow.class) and it worked; no freeze and normal window.

Apparently there is more to the problem than the GUI prefs gadget setting. I guess my next step will be to reinstall OS4.1FE on my alternate boot partition and see what happens when I start reinstalling OS4.1FEu1 and Enhancer stuff.

@xenic

The main prefs only affects thyeWorkbench and SA_LikeWorkbench screens.

You need to set it up for the default screen type in Screen prefs to IIRC.

[edit]
Check that <<default>> is set to Like WorkBench on the GUI tab, by default it defaults to errm Use defaults (which looks abit 3.1ish)

@broadblues
Quote:

Did that but nothing changed. I did install a backup of my original OS4.1FE install on an alternate boot partition. I added 'shared.image' and 'infowindow.class' so I could test the Multiviewer 'About' window on the FE partition. I changed the priority of the FE partition so that it's the primary boot partition. After a hard reboot, I tested Multiviewer with a Gadget background image and without a Gadget background image. It now works as it previously did; with the background image no problem & without the background image a freeze.

Tomorrow I need to start reinstalling update1 & Enhancer stuff to see if I can determine what else is affecting the window.class freeze and fix my normal boot partition.

@broadblues

Thank you

@xenic

Quote:
The funny thing is that this bug has been fixed in the OS4 beta for almost half a year now. But now that OS fixes are not delivered via AmiUpdate, we'll have to wait for a new update pack (which is scheduled for when-it's-done).

@trixie
Quote:
Since someone seems to think that updates must be delivered at a computer show or for Christmas, I think we'll be waiting at least another 4-7 months (suppressing long rant)

As I pointed out to Andy, booting from an old FE partition eliminated my window.class related freeze. Since that post I've narrowed down the problem to something in my DEVS: directory; probably my datatypes. I have a complicated System partition with lots of "assign added" directories for 3rd party software so it will take me another day or two to isolate the exact cause of my freeze.

@all
For anyone who might be interrested, I solved my additional freeze problem. I had to remove my WarpPNG datatype. The WarpPNG datatype works fine for image viewers like Multiview, Multiviewer etc. but causes freezes with some programs (DiskImageGUI) or Infowindow.class that crash in window.class. Until a fixed window.class is released I won't know if the real problem is in window.class or the WarpPNG datatype.

@broadblues

CANDI (Full Version) 1.3 (23.11.2015)

There is a reproducable crash which i already reported to the coders (but i got no feedback, so it might as well be in the bug list already).

I'll report it here so it won't be forgotten.

Steps to reproduce:
1) Start CANDI (i have "Default Light v1.7 running on a custom background)
2) Insert an USB stick
3) Right-click on it's icon to bring up information
4) Choose any disk.icon and move it to the USB icon in Information
5) Save

It will reproducably crash *every* time i do this.
Even if i give the very same disk icon that is already installed.
It looks as if there is a problem with updating the screen resp. the CANDI animation after the icon has been saved and the USB icon is updated/redrawn on screen.

Why it only happens with USB devices i don't know, maybe CANDI falls over because the save and redraw/update is slower as with HDD/RAM devices, because those don't trigger the bug.



P.S: Is there a CANDI animation editor planned?
So people can create their own stuff and share?

I dream of a CANDI animation just like the DefaultLight but with dandelion seeds...rotating dandelion seeds...

P.P.S: There is also a typo in the CANDI animation list.
The Fireworks animation has a description that says
Quote:...probably because of too much bubble water.

@Raziel
about
...
P.P.S: There is also a typo in the CANDI animation list.
The Fireworks animation has a description that says
Quote:
hayppy new year
...

Try to edit Fireworks icon and fix comment.