Welcome, Guest. Please login or register.

Author Topic: AmigaOS Classic - Solid Window Dragging  (Read 183 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AncalimonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 522
  • Country: 00
    • Show only replies by Ancalimon
    • http://www.myspace.com/orhunmusic
AmigaOS Classic - Solid Window Dragging
« on: April 24, 2024, 05:11:50 PM »
Are other programs enabling solid window dragging apart from mcp and powerwindows on AmigaOS 3 ?

What I would like is a utility with this sole purpose preferable that works better with new intuition and layers from AmigaOS 3.2
A4000T, 604e@400&060@66, 128MB+16MB+Zorram256, CVisionPPC, VLabMotion, Toccata, XSurf100&RapidRoad, Prisma Megamix

A1200, Blizzard060@50, 256MB, Blizzard IV SCSI, FastATA mk4
 

Offline Thomas


Offline AncalimonTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 522
  • Country: 00
    • Show only replies by Ancalimon
    • http://www.myspace.com/orhunmusic
Re: AmigaOS Classic - Solid Window Dragging
« Reply #2 on: April 25, 2024, 05:37:29 PM »
I totally forgot I had this :)

Is there a way to maybe reduce priority? Moving it over icons caused amigamp to cut out the module playing.

Also can the program be modified so that it does not drag the window from the top two pixels of the upper window border? Using the new intuition.library resize windows from all four borders, the top border resizing does not work.
« Last Edit: April 25, 2024, 05:59:49 PM by Ancalimon »
A4000T, 604e@400&060@66, 128MB+16MB+Zorram256, CVisionPPC, VLabMotion, Toccata, XSurf100&RapidRoad, Prisma Megamix

A1200, Blizzard060@50, 256MB, Blizzard IV SCSI, FastATA mk4
 

Offline Thomas

Re: AmigaOS Classic - Solid Window Dragging
« Reply #3 on: April 27, 2024, 04:24:53 PM »
can the program be modified so that it does not drag the window from the top two pixels of the upper window border?

Done :)

Quote
Is there a way to maybe reduce priority?

No, unfortunately not. Window movement is an asyncronous process. SolidWin only calls the function which tells Intuition that a window shall be moved. Intuition records this information and later executes it when it fits into its business, probably in the context of input.device.

Quote
Moving it over icons caused amigamp to cut out the module playing.

Window movement should not need such a lot of CPU. But it probably locks the screen for other drawing. So if AmigaAMP plays its music in the same task which updates the window, then window movement might stop it from playing. This cannot be bypassed by a priority change. AmigaAMP would have to be redesigned to play music independently from drawing.