|
|
Rank: Advanced Member
Groups: Member
Joined: 5/28/2009
Posts: 70
Location: Cheshire, UK
|
I have tried the web generally and this forum for a solution to this but can find nothing relavent. When my default workbook opens on running ProcessBook I can see few of my Display entries until I maximise it. I would like the ProcessBook to maximise automatically, to fill the screen, on opening. I can do a bit of VBA and have looked for the ProcessBook equivalent of Excels "Workbook_Open()" event. Unless a ProcessBook display is opened I cannot do anything in the VBE as most menus options are greyed out and disabled. I am assuming that this is one of those things that "cannot be done".  regards, Miles MilesUK
ProcessBook v3.0.15.3
|
|
|
|
|
OSIsoft vCampus is a subscription-based, online offering that consists of providing everything people need to develop applications on the PI System. We invite you to take a "tour" of the OSIsoft Virtual Campus - also feel free to consult the FAQ or contact OSIsoft vCampus for more details.
|
|
|
Rank: Administration
Groups: Administration
Joined: 6/20/2008
Posts: 612
Location: Cheshire, United Kingdom.
|
Hi Miles, There are options...  First one would be to create a .Net ProcessBook addin, this way you can respond to application level events without opening a display first, these events include openeing of PIW's. If you work in a locked environment, this is going to be a little difficult to implement. Second, if you are talking about the ProcessBook application as a whole, then you can manipulate the ProcBook.ini file for the overall size by altering the WindowPos value in the Startup section. If you are talking about a PIW then ignore this one. Third, would be to create a little executable that you use inside of a shortcut (that ultimately points to procbook.exe). The exe simply runs ProcessBook but hangs around until it sees a PIW being opened (your default PIW) then maximises and shuts down. Bit like a ProcessBook startup executable to prepare your environment for how you like it. All not as nice as you would have liked I am sure...a .Net addin provides the best (and likely OSI supported) method, the third is a little more realistic and quicker to implements. Both mean distributing something extra than the PIW file itself. Cheers, Rhys. Principal Consultant
Real-Time Data Management @ Wipro Technologies
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/28/2009
Posts: 70
Location: Cheshire, UK
|
Rhys, As always you present more than one possible solution. Thank you. You are right in that I am trying to maximise a PIW file (that is set to auto load on running ProcessBook under Tools-->Preferences, Start tab). Option 2 ruled out. Unfortunately we are locked down so option 1 is out also. Deployment is for myself only so option three seems to be realistic but I would not know where to start. Could you point me to any resources to get me going please. Miles EDIT: Actually I'm being daft here.  I have just realised that I'm trying to find a sledge hammer to crack the proverbial nut. 
I'll be realistic and continue to use the maximise button.  Thank you again though for your inputMiles MilesUK
ProcessBook v3.0.15.3
|
|
|
Rank: Member
Groups: Member
Joined: 10/7/2009
Posts: 14
|
I know this post is over a year old, but isn't this all you are after: Code:Private Sub Display_Open()
Application.Maximize
End Sub Place this in the startup file and you should be fine.
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/28/2009
Posts: 70
Location: Cheshire, UK
|
jc113883, I was after a solution to maximise the actual Processbook (e.g. Miles Sheets.PIW) as opposed to the individual displays. My Processbook list of displays occupies less than half of the actual application window - consequently many of the Processbook Entries are not being shown until I manually maximise the list. For example: Code:+---------+
|+---+ |
|| | |
|+---+ |
| |
+---------+
when I would like this Code:+---------+
|+-------+|
|| ||
|| ||
|| ||
|+-------+|
+---------+
thank you for taking the time to post though. :-) miles MilesUK
ProcessBook v3.0.15.3
|
|
|
Rank: Member
Groups: Member
Joined: 10/7/2009
Posts: 14
|
Ah, I see. Sorry, I was confused between Processbook the application and a processbook PIW file. I don't really use PIWs! The only thing I can think of which you've probably already considered is to make your startup file a Processbook display file, which maximises itself, opens your PIW file and then closes itself, essentially giving you the same thing you were after, like so: Code:Private Sub Display_Open() Me.Maximize Application.ProcBooks.Open ("<PBook path>") Me.Close (False) End Sub If the display is maximised, then the PIW file will open maximised. Graeme.
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/28/2009
Posts: 70
Location: Cheshire, UK
|
jc, that IS neat. And quick. Cheers. miles MilesUK
ProcessBook v3.0.15.3
|
|
|
|
Guest
|
