This work for a few images, but let's say that your app has 100's images. Your
package / SA has limits.
I found it easy to settle on a routine. Images 400 X 400 or less I produce at
800 X 800 and run them the TinyJPG and get optimized. So the 2X size work well,
in fact in "mandatory" on small
Thanks for the tip Ralphlove the sound of that filer function.
On Tue, Jun 12, 2018 at 7:00 PM, Curry Kenworthy via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> Optimizing scripts in LC is not the same as running reports in other
> software suites. If you only need 10 results, you
Optimizing scripts in LC is not the same as running reports in other
software suites. If you only need 10 results, you probably don't want to
handle all items twice.
I hate to loop through all items even once. But if I do, I may be done!
I'm not making a full report to print out; I'm just g
Filter is lightning fast. I have the list of all 40,000+ cities in the US
and have a predictive search field. I tried DBs, in memory DB and other
methods until I stumbled on to the filter operator. Load a text file into a
var and the start filtering. There is no perceptible delay when typing the
fi
Then there's something about Geoff's problem (or problem statement) that
I don't understand.
What on earth is in those records for sorting a mere 2000 of them to be
noticable? (I had thought he had to be talking about magnitudes more
lines than that).
LC (9.0) sorts 20,000 lines of >1000 cha
Just one thing to add here based on what Trevor mentioned - these are images
which you have complete control over so...
If you can upscale them (perhaps using the tool Lagi suggests) with a good
degree of visual improvement then you can use the multi-resolution aware
feature of referenced (file
The scenario Geoff described is roughly to get the
top ten (a handful) of 2000 records comparing a certain
numeric value of each.
To get that unknown value of each one has to go once through
all the records *and then sort* for that ranking.
(LiveCode is very fast with a simple numeric sort!)
Any ot
Put yourself in the computer's shoes, and also clarify what you need to
accomplish. You are asking it to sort the entire list of 2000 records,
but (if I understand) you only want a handful of those.
And it has already gone through all the records once before the sort. If
you asked a human t
Hi Paul
Yeah, thats probably the only way to track it down is to know what data is
in the column. however. what happens when you paste an invalid
path into an image's file path boxdoes it return an error or crash.
or does it just give you a blank image?
If I recall correctly
I don't know if these are good ideas or BAD ideas and without some
suitable data, not sure if I could find out - so I'll throw the ideas
over and let you decide if they are worth trying :-)
1. Two ideas combined
- avoid scanning for the "item 1" of each line
- use the (hopefully optimi
I should have noted the LC version. This is a standalone built under
LiveCode 6.7.11
If I could get one of the customers to respond with their document(s)
and settings that caused the error, it would probably be simple to track
down.
My current theory is that rows can display either htmlText or a
on Tue, 12 Jun 2018, Lagi Pittas wrote:
> I don't know what sort of images you have but
> take a look at xara (xara.com/designer-pro/features)
I use Xara Photo Graphic Designer and agree with Lagi's
recommendation. Check these videos about intelligent scaling:
https://www.youtube.com/watch?v=dfNL
On Tue, Jun 12, 2018 at 2:01 AM, Tiemo Hollmann TB via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> I thought the dpi only reflects at print, because any screen has it's fixed
> pixels. I think an image 800x600 with 144 dpi looks identical on any
> screen,
> as an image 800x600 with 72
so i work alot with datagrids and i've never seen such an array of errors.
Can you tell us what version of LC the standalone was built with?
one thing that comes to mind is something i vaguely remember happening a
few years ago. I was updating the datagrid while one of the handlers in
the library
The LC team takes custom requests, and you wouldn't have to tell them how
to link the code into LiveCode. :) Write to supp...@livecode.com and see
what they say.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 12, 2018 10:19:54 AM
You may be right, I should have said to double the size. The idea is to
give LC more pixels to work with when it scales the card content. But LC is
pretty good at scaling, so starting with the originals may work fine.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | h
Thanks for the reply, Jacqueline. I was hoping for a reply from you as one of
the Android experts on this list.
Your response is as expected. Yes, I am aware of Bluetooth usage on Android..
and, ideally, THAT would be perfect... since I have a fully developed and
working iOS version of my app
If you use fullscreenmode they will scale automatically, you don't have to
do anything. Everything on the card will resize itself proportionally,
which is why it's so easy.
The down side is that buttons and other controls will also scale, so they
may not be exactly the same size as standard OS
Are you talking about the geometry manager? I’ll be talking about that at LCG
next month.
One thing you’re going to need to handle manually will be the aspect ratio. The
GM does not have the ability to do that automatically (that I know of).
To prevent accumulation of small errors in your resiz
Sorry, I forgot to mention Jerry who already proposed to pull out computations
from the inner loop and also to use variables in the inner loop. My experience
says to avoid getting items as often as possible. And to use the random() in the
inner repeat loop instead of in the final sort may be worth
I have a rarely occurring Datagrid error that a couple customers have
reported. Unfortunately, none of the customers have been able to tell us
what they were doing when the error occured or be able to reproduce it.
I hope someone on this list may have seen this before and know what is
causing it.
You could try the following:
repeat for each key T in interestArray[uID]
put item 1 of interestArray[uID][T] into i1
put item 2 of interestArray[uID][T] into i2
repeat for each line S in storyArray[T]
put userSeenArray[uID][item 1 of S] into s1
put abs(item 2 of S - i1) into s2
i
Hi,
I have a full-window image and need dozens of clickable transparent polygons
on top of it, shaping details of the image. My idea was, that all these
polygons could be resized and positioned automatically by the scaling
property of the object, when resizing the stack.
I have never used the
Hi Lagi,
faszinating tool!
Tiemo
-Ursprüngliche Nachricht-
Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von
Lagi Pittas via use-livecode
Gesendet: Dienstag, 12. Juni 2018 11:18
An: How to use LiveCode
Cc: Lagi Pittas
Betreff: Re: Best practise approach f
Hi,
I don't know what sort of images you have but take a look at xara (
xara.com/designer-pro/features)
Scroll down to the intelligent scaling video - better yet they have a trial.
I think the intelligent scaling might even give you the "safe Zone" that SB
mentioned
Regards Lagi
Lagi
On Mon,
Hi Geoff,
One thing to try in your original code, which should be significantly
faster if the array is big, is using
> repeat for each key T in interestArray[uID]
instead of
> repeat for each line T in the keys of interestArray[uID]
The latter has to allocate memory for a string containing all
I know that this might be a different use-case but I have a CA Lottery -
Fantasy five lottery parser that collects lottery data and loads it into a
matrix and provides the total number of hits for each number. This also has 4
optimization buttons to the show differences. This aupplication was o
Hi Jacque,
I thought the dpi only reflects at print, because any screen has it's fixed
pixels. I think an image 800x600 with 144 dpi looks identical on any screen,
as an image 800x600 with 72 dpi because in both cases 800x600 screen pixels
are being used and there is nothing between the pixels. Or
28 matches
Mail list logo
