Welcome Guest ( Log In | Register )

Reply to this topicStart new topic
> Drag & Drop From Foc
post Nov 3 2007, 10:51 AM
Post #1

Forum Member

Group: Members
Posts: 2
Joined: 3-November 07
Member No.: 2,467

After having finally upgraded from PMView 2.32 to 3.51 I notice a different behaviour of drag & drop operations. It seems impossible now to drag an icon from the foc to the rectangle for icons in the icon's settings notebook. With the old version this worked perfectly. Any hint?

Ciao, Harald
Go to the top of the page
+Quote Post
post Dec 7 2007, 01:53 PM
Post #2

Forum Member

Group: Admin
Posts: 667
Joined: 14-March 00
From: Wilmington, North Carolina
Member No.: 3

PMView 2000 used a separate WPS class (PMVDDROP.DLL aka PMView Drag&Drop Daemon). This class existed on the system in form of a hidden desktop object and was needed to provide Drag&Drop support for OS/2 v2.x, since OS/2 did not provide D&D support through any of the regular APIs. The only way to do it was through SOM.

The WPS class had its problems. If the computer was wiped (or the OS/2 registry was wiped) and PMView was "reinstalled" by simply copying the files, then Drag&Drop would not work, as the Daemon object was not registered and running.

Another issue was that the "hidden" object was not always invisible. Users with Object Desktop or other enhancers installed, could possibly see the object on their desktop.

These two issues (especially the former) were causing quite a few support requests and annoyance to users.

With Warp 3, IBM introduced APIs that let applications provide drag & drop of files without the need for registering with SOM. PMView/2 and PMView 2000 did not use the new API, as they must also be able to run on OS/2 v2.x (versions prior to Warp 3).

PMView Pro requires Warp 3, and since most OS/2 applications support the interface provided by the new Drag & Drop APIs, we decided to switch to using them instead of using the WPS class. The only side effect is that dropping files in the WPS area for setting icons no longer works. The reason for this is that the icon setter does not accept the file objects returned by the APIs. Arguably this is an OS/2 bug. When the new interfaces were added to Warp 3, the icon setter component should have been updated too. Unfortunately this did not happen...

It is unfortunate that this change broke some functionality, but the fact is that the new behavior works out better for the majority of users. Back in the days of PMView/2 and PMView 2000 I used to get several e-mails a week from people with broken drag & drop (usually as a result of wiping/restoring their OS2.INI or reinstalling OS/2 without reinstalling PMView).

Peter Nielsen ( "If you can dream it, you can do it" JFK.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


Lo-Fi Version Time is now: 28th January 2020 - 08:55 AM