File Naming

Michael Correll mcorrell at memphisbusiness.com
Sun Jul 6 23:03:31 PDT 2008


Jack:

Again off the top....  perhaps listwindows(  since it builds an array  
of open windows associated with a particular file in front to back  
order.  The first window in the array would be the new window.   
ArraySize( could be used to determine if a new window has been added  
to the listwindows( array and an  ExecuteASAP procedure could  
continually check for the presence of that new array element -- i.e.,  
a new window.

All this is just a quick idea.  I'm sure those who are much more  
proficient than I am could work out a procedure like this much  
quicker than I could.  Or maybe come up with a better approach  
altogether.  But if I understand your question correctly, this is one  
way I might approach it.

MC.

--
Michael Correll


On Jul 7, 2008, at 12:19 AM, Jack Stewart wrote:

> Thanks a lot Michael.
>
> If I could figure out how to trigger a procedure anytime a new  
> window is opened or brought to the front, I could easily make it  
> work with a combination of Windowname and info("windowname". I  
> don't know how to detect the presense of a new window regardless of  
> how it was created.
>
>     Jack
> On 7/6/08, Michael Correll said ……
>
>>
>> I see what you mean now.  That is indeed a horse of a different
>> color.  And the fact that the user can create more windows
>> complicates things.
>> This is not ideal, but perhaps you could use an AWT box in a
>> relatively inconspicuous corner of the window and display the file
>> name or window name or other information with one or more of the
>> various info( functions?  Not necessarily pretty....but it could  
>> work.
>>
>> That's the best I can come up with off the top right now.  I suspect
>> others here may have a better solution for you.
>>
>> MC.
>>
>> --
>> Michael Correll
>>
>>
>> On Jul 6, 2008, at 11:31 PM, Jack Stewart wrote:
>>
>>> Thanks Michael. You are right but this is specifically what I am
>>> trying to avoid having to do for every window in the db.
>>>
>>> The problem is that I want a longer file name than Panorama allows,
>>> (even though OS X allows it). My user finds it very helpful to
>>> include certain info such as version number in the actual file
>>> name. I don't care at all if it displays in the window but I don't
>>> want to have to trigger a procedure for each menu opened window
>>> simply to change the window name. The user is free to create more
>>> windows which can create a programming nightmare.
>>>
>>>             Jack
>>>
>>>
>>> On 7/6/08, Michael Correll said ……
>>>
>>>>
>>>> I believe the Windowname statement in the procedure that opens the
>>>> window in question will do it.
>>>>
>>>> Example:
>>>>   OpenForm "Old Form Name"
>>>>   WindowName "My New Form Name"
>>>>
>>>> M.
>>>>
>>>> --
>>>> Michael Correll
>>>>
>>>> On Jul 6, 2008, at 10:03 PM, Jack Stewart wrote:
>>>>
>>>>> Does anyone know a SIMPLE way to exclude a part of a Panorama 5.5
>>>>> file name from all window title bars?
>>>>>
>>>>> I don't want to run a script renaming the window each time one of
>>>>> them is opened. I do want to always exclude the last part of the
>>>>> file name from all windows.
>>>>>
>>>>> Thanks -- Jack
>>>>
>>>> _______________________________________________
>>>> Qna mailing list
>>>> Qna at provue.com
>>>> http://provue.com/mailman/listinfo/qna
>>> _______________________________________________
>>> Qna mailing list
>>> Qna at provue.com
>>> http://provue.com/mailman/listinfo/qna
>>
>> _______________________________________________
>> Qna mailing list
>> Qna at provue.com
>> http://provue.com/mailman/listinfo/qna
> _______________________________________________
> Qna mailing list
> Qna at provue.com
> http://provue.com/mailman/listinfo/qna



More information about the Qna mailing list