Ok the title is a bit confusional but i don't know how to explain in better term, limited english from my side you know ..
Aniway today when i worked to a project with NotePad i found a very odd behaviour, this happen with NotePad and some text on it, well a full of text into the NotePad is better for the test
So let's explain in detail:
1 - Open a txt with NotePad (even a normal readme text, you don't need to have a bigger one)
2 - Now move the NotePad window to the extreme left side of the Workbench window, now if you have "screen edges resistance" setted to 0 (in GUI Preference --> control) you have the possibility to move a big part of that NotePad window outside the Workbench area
3 - Now try to increase the NotePad window dimention (using the gadget of the NotePad) to the right side just to fit the entire Workbench screen from left to right
Your NotePad window now should look at screen like this one:
http://imageshack.us/photo/my-images/534/grabcl.png/
4 - Now try to move the NotePad window or redimention its window at the previews size
You should note atleast 2 big problems:
1 - The entire OS will slow down a lot (almost on Sam Flex)
2 - The NotePad window cannot be resized, or atleast with many problems
This test is always reproducible here (SamFlex + Update 3) and of course i don't remember what happen with Update 2 (i discover this just today) so maybe we need to retest this on old system too
Big bug on NotePad or in Workbench/Intuition ?
Re: Big bug on NotePad or in Workbench/Intuition ?
@samo79
I have a SAM Flex 800 (running at 733) and cannot reproduce your problem. I moved notepad halfway off the left side of the screen and then resized it to fill the screen width. I can drag the window around at will and I can resize it smaller (the resize gadget has to be onscreen). I'm using 1280x1024x16 WorkBench screen with compositing turned on. Maybe your problem has something to do with screenmode or another app that's running at the same time.
I have a SAM Flex 800 (running at 733) and cannot reproduce your problem. I moved notepad halfway off the left side of the screen and then resized it to fill the screen width. I can drag the window around at will and I can resize it smaller (the resize gadget has to be onscreen). I'm using 1280x1024x16 WorkBench screen with compositing turned on. Maybe your problem has something to do with screenmode or another app that's running at the same time.
AmigaOne X1000 with 2GB memory - OS4.1 FE
Re: Big bug on NotePad or in Workbench/Intuition ?
Correct, i try your resolution and it's seems better now altrough again a bit slow when you try to move the NotePad's window up/down to the screen (always when the NotePad is opened with some text and increased at full screen from left to right as explain in first post)
Problem happen with my standard resolution (1680*1050) and i think it's a bug because (not to mention the terrible slowdown) i can't resize the NotePad window at all !
Problem happen with my standard resolution (1680*1050) and i think it's a bug because (not to mention the terrible slowdown) i can't resize the NotePad window at all !
Re: Big bug on NotePad or in Workbench/Intuition ?
I tried that and must admit that moving and resizing the window is really jerky und jumpy - but resizing work (and moving as well). Tested on a SAM440ep (Mini, 667 MHz). But I had a lower resolution (32BIt, compositing enabled, 1280x1024).
X1000|II/G4|440ep|2000/060|2000/040|1000
Re: Big bug on NotePad or in Workbench/Intuition ?
Yep at 1280x1024 even if jerky still usable but with an higher resolution it's an hell !
I don't think that problem is into NotePad in general but maybe there is a bug in some Reaction class (don't know what is used in NotePad) as this doesn't happen with any MUI application
Aniway, plz betatester can you open a new ticket for this ?
I don't think that problem is into NotePad in general but maybe there is a bug in some Reaction class (don't know what is used in NotePad) as this doesn't happen with any MUI application

Aniway, plz betatester can you open a new ticket for this ?
Last edited by samo79 on Fri Oct 21, 2011 1:25 am, edited 1 time in total.
- TSK
- Beta Tester
- Posts: 225
- Joined: Mon Dec 20, 2010 1:15 pm
- Location: Home land of Santa C., sauna, sisu and salmiakki
Re: Big bug on NotePad or in Workbench/Intuition ?
@samo79
Any chance you're running out of video memory ? And also running out of fast memory at the same time ?
Any chance you're running out of video memory ? And also running out of fast memory at the same time ?
Keep the party going !
Re: Big bug on NotePad or in Workbench/Intuition ?
Well i have 128 MB of video RAM (ATI Radeon 9250 128MB 64 Bit) and 1 GB of RAM so i doubt i miss the necessary video mem or RAM, but to be sure i repeat the same test again and again after an hard reset (with only NotePad opened and nothing else) ...
It's faster if i use lowest resolutions such 1024*768 or 1280*1024 but problem still the similar aniway ...
It's faster if i use lowest resolutions such 1024*768 or 1280*1024 but problem still the similar aniway ...
Re: Big bug on NotePad or in Workbench/Intuition ?
Just for fun (ehm ..) i repeat again the same test at 1680*1050 and this time i get a freeze instead ...
Something "broken" somewhere i think ..

Something "broken" somewhere i think ..
Re: Big bug on NotePad or in Workbench/Intuition ?
I have a similar report to cha05e90: slow to move, enough to cause hiccup in TN local Vorbis playback, but resizing worked. 1280x1024, AmigaOne, 128 MB graphics memory.
* AmigaOneXE 750FX 512+0 MB RAM, Radeon 9200, sii3112ide, DVDRW ~ AmigaOS 4.1 Final
- tonyw
- AmigaOS Core Developer
- Posts: 1483
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: Big bug on NotePad or in Workbench/Intuition ?
@samo79:
Instead of using a smaller resolution, try repeating the test with a smaller number of bits, eg use 8-bit or 16-bit WB screen at the same screen size. You could also try turning off compositing on the WB screen.
Instead of using a smaller resolution, try repeating the test with a smaller number of bits, eg use 8-bit or 16-bit WB screen at the same screen size. You could also try turning off compositing on the WB screen.
cheers
tony
tony