PMView.com

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Bug When Cmdline-calling Pmview Pro?
gaea
post Jun 30 2005, 12:32 PM
Post #1


Forum Member


Group: Members
Posts: 1
Joined: 30-June 05
Member No.: 192



I think there is a bug in Pmview Pro v3.10 that shows when it's called from the command line to select a group of files.

I have both Pmview Pro v3.10 and Pmview2000 v2.32 installed. They live in separate directories and is called from the command line with two different batch files.

Pmview.cmd (for Pmview 2000):

@echo off
setlocal
set path=g:\os2ut\pmv2000;%path%;
set PMVIEW_INI=g:\os2ut\pmv2000\pmview.ini
pmview.exe %1
endlocal

Pmvpro.cmd (for Pmview Pro v3.10):

@echo off
setlocal
set path=g:\os2ut\Warpin\Apps\Pmview;%path%;
set PMVIEW_INI=g:\os2ut\Warpin\Apps\Pmview\Pmview.ini
pmview.exe %1
endlocal

Now I go to g:\ftp\brides directory to view all Bridesandbeauties pics. First I do it
in Pmview 2000:

Pmview.cmd Bridesandbeauties*.*

The File Open Container (FOC) pops up showing thumbnails of all Bridesandbeauties files. To view one, I click on the thumbnail and the main window opens with the selected file.. This is the behaviour I've seen in Pmview from the beginning.

Next I do it in Pmview Pro:

Pmvpro.cmd Bridesandbeauties*.*

What happens now is NOT what I expect from Pmview Pro. The Main window opens showing the FIRST Bridesandbeauties file in the directory. The FOC is NOT open at this point so I open it with Ctrl+O, expecting to see thumbnails of all Bridesandbeauties files. Instead, it shows thumbnails of ALL pics, not just the Bridesandbeauties pics! As g:\ftp\brides contains a LOT of pics, this will slow down my system a lot and make it hard for me to find only the Bridesandbeauties thumbnails in the FOC.

Is this behaviour intentional or is it a bug?
Go to the top of the page
 
+Quote Post
Peter
post Jul 5 2005, 01:33 PM
Post #2


Forum Member


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



QUOTE (gaea @ Jun 30 2005, 01:32 PM)
Is this behaviour intentional or is it a bug?


It is intentional. Starting with PMView Pro (v3.00), a wild card on the command line will load the file sequencer. (Prior PMView versions used to open up the FOC and set the FOC filter).

For instance, say that you have these files on your hard drive:

d:\private\secret1.gif
d:\private\secret2.gif
d:\private\secret1.jpg
d:\private\secret2.jpg
d:\jpeg\my_house.jpg
d:\jpeg\my_house001.jpg
d:\jpeg\my_house002.jpg
d:\animals\dog01.tif
d:\animals\dog01.jpg

Then start PMView with:

pmview d:\private\*.gif d:\jpeg\my_house???.jpg d:\animals\*

This will load the file sequencer accordingly: When you press PGDN/PGUP, PMView will show the 6 files matching the masks provided on the command line:

d:\private\secret1.gif
d:\private\secret2.gif
d:\jpeg\my_house001.jpg
d:\jpeg\my_house002.jpg
d:\animals\dog01.tif
d:\animals\dog01.jpg

You could add the /print flag to the command line and get the images printed instead of loaded into the sequencer.

The change was made by user request and also in order to streamline the functionality of PMView.

Currently there is no command flag for opening the FOC from the command line. I may consider adding this in a future version if it turns out that there is a need for this functionality.

Thanks,


--------------------
Peter Nielsen (peter@pmview.com) "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: 18th August 2018 - 11:14 AM