New Macs – Unzip Omnis
I’ll write it up and send over tomorrow for you.
Mike Matthews, Managing Director, Lineal Software Solutions Ltd
Apple Reseller, Microsoft Partner, SQLWorks Business Partner
phone: 01271 375999
On 26 Sep 2017, at 23:10, Michael Mantkowski <michaelj@clientrax.com <mailto:michaelj@clientrax.com>> wrote:
> Hi Mike,
>
> Yes, that is exactly what I am trying to do.
>
> I am currently working on v4.
>
> I am curious, in the past I tried to do what you are suggesting but was not able to because Omnis Opens the files when it starts. So trying to delete the file did not work.
>
> I would be curious if you would share the code snippet you did this with? My application actually creates its open update library when it sees there is a new version available allowing my application to essentially update itself when the users starts it. But it never worked with the XCOMP or EXTERNAL files because I was using Omnis as the updater which opened the files I wanted to replace.
>
> Michael
>
> *********************************************************************
> Michael Mantkowski
> ClienTrax Software
> 1-614-875-2245
> *********************************************************************
>
>
> —–Original Message—–
> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com
> Sent: Tuesday, September 26, 2017 5:58 PM
> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com <mailto:omnisdev-en@lists.omnis-dev.com>>
> Subject: Re: New Macs – Unzip Omnis
>
> Ok, so reading back a bit, OSX and Studio what version? I don’t think it matters.
>
> I currently have done this by using the FileOps commands from the running version of Studio. You know where the comps path is using SYS() functions.
>
> I move the current ones into a new folder called comps-disabled.
> Then move the new ones into place.
> The restart Omnis.
>
> This worked for v4, v5 and v6 so far, OSX and Windows.
>
> The trick is not to replace a current loaded one, but you can move it around while running. So I move it out, put in the new one, and force the user to restart our App.
>
> This works for Externals as well. Did I get the problem right now?
>
> Mike
>
> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>
> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
> phone: 01271 375999 | web: lineal.co.uk <lineal.co.uk/> <www.lineal.co.uk/ <www.lineal.co.uk/>> | email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk> <mailto:mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>>
>> On 26 Sep 2017, at 22:51, Michael Mantkowski <michaelj@clientrax.com <mailto:michaelj@clientrax.com>> wrote:
>>
>> Mike,
>>
>> I think there is a misunderstanding. I am trying to update an already existing instillation.
>>
>> Just trying to get a few new XCOMP file updates into the exiting OmnisRT.
>>
>> *********************************************************************
>> Michael Mantkowski
>> ClienTrax Software
>> 1-614-875-2245
>> *********************************************************************
>>
>>
>> —–Original Message—–
>> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com
>> Behalf Of Mike Matthews
>> Sent: Tuesday, September 26, 2017 5:46 PM
>> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com <mailto:omnisdev-en@lists.omnis-dev.com>>
>> Subject: Re: New Macs – Unzip Omnis
>>
>> Michael,
>>
>> You need to look at and understand the FirstRunInstall mechanism. I think thismighthelp you, the penny finally dropped for me the other day, after a good sound ear bashing by Chris at Omnis Support.
>>
>> Mike
>>
>>
>>
>> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>>
>> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
>> phone: 01271 375999 | web: lineal.co.uk <lineal.co.uk/> <www.lineal.co.uk/ <www.lineal.co.uk/>> |
>> email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk> <mailto:mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>>
>>> On 26 Sep 2017, at 22:36, Michael Mantkowski <michaelj@clientrax.com <mailto:michaelj@clientrax.com>> wrote:
>>>
>>> Alex,
>>>
>>> That would not work because the xcomps reside within the OmnisRT.aps file (package). I don’t want to replace the whole OmnisRT, just the three xcomps the are inside it.
>>>
>>> But maybe if I manually create the folders the represent the path?
>>>
>>> I will try that.
>>>>>
>>>>> **************************************************
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com