I found a bug in Workbench. If you resize the "Find" window while it's working you get a Grim Reaper. How do you report bugs?

_________________
AmigaOne 500(update 6) / microA1(update 6) / Cubic IDE / Imagine
Amiga 4000/1200/500/2500/1000 / VIC20 / C64 / SX64 / C128 / C16 / C116 / Plus/4 / PET B500
Windows 7 / 3GHz AMD Phenom 8GB RAM / Lightwave / Visual C++

@thinkchip

Register http://forum.hyperion-entertainment.biz/

If you think its OS general not SAM460 specific report it here
http://forum.hyperion-entertainment.biz/viewforum.php?f=14&sid=9c25789b4e751f061704a083ed07cf08

_________________
AF 2012, Hollywood Designer 5, AmigaOS 3.5,4.0 and 4.1 registered user, user of Linux Mint 13
Roots Taking Over The World

@thinkchip

Mmm just tried but i didn't got any crash on my system, btw you can fill you report on the Hyperion's forum
I suggest you to include also your Grim Reaper log.

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@thinkchip

Tryed to reproduce and can't. If you can give me a steps of how to reproduce the problem, i will fill out bug report for sure.

_________________
aos4/aros/mos projects & articles

If you like any amiga related work i do, feel free to donate

@thinkchip

Quote:

I found a bug in Workbench. If you resize the "Find" window while it's working you get a Grim Reaper. How do you report bugs?

Ideally by starting a thread on the hyperion forums.

I just tried finding something from find via the WB menu item.

I resized the window, back and forth zoomed it and iconified uniconfied it all whilst it was working. No crash.

Can you provide more info on reproducing this? And a log of the crash. Does it happen repeatedly foryou or was it a one off?

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Before I report it, I'll see if I can reproduce it. I think a lot of people resize the find window.

_________________
AmigaOne 500(update 6) / microA1(update 6) / Cubic IDE / Imagine
Amiga 4000/1200/500/2500/1000 / VIC20 / C64 / SX64 / C128 / C16 / C116 / Plus/4 / PET B500
Windows 7 / 3GHz AMD Phenom 8GB RAM / Lightwave / Visual C++

Does anyone know if they ever 'fixed' a 'bug' in Intuition that I experienced?

When you had checkmarked items, Intuition 3.9 (and earlier) would draw the selected image before updating the checked status, when you clicked on the menu item.

In my situation, I had the same BOOPSI image for both the selected and unselected images and took over the checkmark drawing so consequently it was difficult to know whether to draw the item checked or not. More accurately I took over the whole menu drawing which is why I couldn't just have two different BOOPSI objects.

I managed a bodgy work-a-round but hopefully its not necessary anymore.

Looking forward to an X1000 call-up one day hopefully from the 2nd round. I think they are still working through the first round...

@thinkchip

I've noticed another bug in Find where the size column is too small and cannot be resized to reveil the full size of a file it found.

I might file a bug on it when I get home.

_________________
>Amiga Classic and OS4 developer for OnyxSoft.
>A1-XE/G4, Radeon9250, Sweex 5.1, SII680
-Don't hesitate to contact me about my programs, but please use e-mail instead of PM. E-mails are more likely to be read in time, and easier for me to keep track of.

@gonegahgah

I've noticed in YAM that if I have a menu item selected I possibly activated with the left mouse that the item is not selected in the program. If I bring up the menu again it is checked but the program doesn't act as if it is. I usally have to uncheck then check it again and it works.

This happens with my YAM Edit->Type and spell menu item.

@thinkchip

Can't replicate the bug on OS 4.1.4 on A1XE G4.

@Hypex

That one sounds possibly more like an app bug to a known situation I think. Menu item messages can come in any order and can't themselves be relied upon to determine the final state of the checkmarks. I'm fairly sure the docs say that apps should check the state of the checkmarks when they receive a menu item message rather than relying upon that message. If it isn't a YAM bug then that's certainly curious. You probably won't find this happening in other apps? Might be worthwhile to see if others experience the same thing..

The 'bug' that I found I can see why it would have been there. Intuition probably does things in the following order:

1. Draw selected image.
2. Set checkmark status to on. (or to off).
3. Draw checkmark.

What I would rather they do is:

1. Set checkmark status to on. (or to off).
2. Draw selected image.
3. Draw checkmark.

Under normal circumstances the top sequence does no harm to anyone but for my more involved - but system friendly - menu items it means finding cludgy work-a-rounds.

Last edited by gonegahgah on 14-May-2012 at 10:33 PM.