My first guess would be to find a MacOS PDF editing application that is
either AppleScript-able, or experiment with using Automator. The
alternative might be just cracking open the binary of the PDF file in LC
and see what you find.
___
use-livecode maili
Yes, that is the section of code that I was referring to. So you should be
able to:
lipo revsecurity.dylib -remove i386 -output revsecurity.dylib
After changing to the directory containing the file in the terminal.
>
>
___
use-livecode mailing list
us
Hi Brian,
I am assuming you are referring to the following:
-- Remove unneeded slices from the MacOS externals
if the platform is "macos" and pSettings is not empty then
local tRemove
if pSettings["MacOSX x86-64"] is true and pSettings["MacOSX x86-32"] is not
true then
put "i386" into tRemov
Hi Brian,
I have not tried manually running lipo on the file.
I figure I will have to resign the app anyway so
not a huge deal if it works.
I’m not a big unix user so if you have some
additional suggested lipo code for me to look
at I’d appreciate it.
All I found on the web was the following
r
LC already has code to run lipo when building the app. It currently just
operates on externals. The code is in __revSBCopyFile which is a part of
revsblibrary.livecodescript. From my initial look, I'm guessing that it
also needs to work on revsecurity.dylib as well.
Have you tried manually runn
On Mon, Nov 26, 2018 at 3:08 PM Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Try the field object.
>
Not that this couldn't be worked around, but isn't a field limited in the
width of what it can display? i.e. put a single line 100,000 characters
long into an un-wrapp
That sounds like the solution.
JB
> On Nov 27, 2018, at 4:44 PM, Rick Harrison via use-livecode
> wrote:
>
> Hi JB,
>
> I had the build for Mac OS X 64-bit box checked in the
> Standalone Application Settings for my stack.
>
> I am running High Sierra and so far LiveCode does
> not yet that
Hi JB,
I had the build for Mac OS X 64-bit box checked in the
Standalone Application Settings for my stack.
I am running High Sierra and so far LiveCode does
not yet that I know of support Mojave. I do however
think that yes this is Apple forcing things forward as
per usual.
I believe the team
On 27/11/2018 18:34, Richard Gaskin via use-livecode wrote:
The existing field object does a fine job buffering for smooth
scrolling of just about any text of practical length. Logically, the
limit of field contents is about 4GB (UINT4), but in practical terms
other memory needs may not al
I have never submitted an app on the apple store but
I googled i386 and here is what I get.
x86_64 is for 64 bit processors. i386 is for 32 bit processors.
So the question I wonder is does this have something to do with
Mojave OS? From what I have read they will be eliminating the
32 bit program
LC version 9.0.1
Rick
> On Nov 27, 2018, at 12:38 PM, Brian Milby via use-livecode
> wrote:
>
> What version of LC?
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscript
What really needs to happen is that the DG or table field visual display is
loaded under script control. So the idea of jumping from a display of
columns 1-10 over to 6000-6010 is managed live, using the scrollbarDrag
message as the thumb is moved. What the user sees during that process is a
matter
Folks,
Can anyone using LC Server with revIgniter share any tips on why new controller
pages might throw 404 errors, even if they contains the content from the
(working) welcome.lc controller or blog.lc example from the revIgniter docs…?
https://revigniter.com/userGuide/general/controllers.html
Alex Tweedly wrote:
> On 25/11/2018 23:04, Richard Gaskin via use-livecode wrote:
>>
>> This limitation may have been eliminated, or close to eliminated,
>> with the field object. And now that fields have column-independent
>> alignment, it's rare that there's ever a need to replace that one
>>
What version of LC?
Thanks,
Brian
On Nov 27, 2018, 11:28 AM -0600, Rick Harrison via use-livecode
, wrote:
> Here is the problem:
>
> lipo -info /Users/…(PathToMyAppContents)…/Contents/MacOS/revsecurity.dylib
> are: i386 x86_64
>
> Notice that at the end it says i386
>
> That is what apple is co
Here is the problem:
lipo -info /Users/…(PathToMyAppContents)…/Contents/MacOS/revsecurity.dylib are:
i386 x86_64
Notice that at the end it says i386
That is what apple is complaining about.
This is clearly a serious LiveCode revsecurity.dylib problem, and without it
fixed
no one can submit a
16 matches
Mail list logo
