Hi Richard,
Subsequent to my previous post, during testing I noticed that the new lc file was corrupted in that field labels disappeared or were replaced by results from the related edit field. At this point in time I have not found anything else wrong, however testing continues.
As for your questions - the new lc file is 1.72mb and the old one is 14.5mb other wise all was the same.
I have a sneaking feeling that the problem originated from v7.0.3rc as I found it corrupted the lc file a few times. When I went to v6.7 I used some option Jacque described to me to save the file for v6.7. From there I used the same lc file for v7.0.4 and v7.0.5 and the size of the lc file has always been large. The new size is a surprise to me (mind you would expect the surprise as I am only learning).
I have had a bit of a play with the Windows compile of the app and it is very quick and seems fine. The other thing I have noticed is that the previous version used to take forever to quit - nice and fast now.
Bye,
Hilton.
Speed of moving from Card to Card
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Re: Speed of moving from Card to Card
Hi Richard,
I checked the original app I wrote (not the one referred to before) and whilst it was slow in the IDE about 4secs to change a card it was not impossible, I noticed that the lc file was 20Mb.
I followed the previous procedure and the file size reduced to 1.2mb and the speed is pretty good now. So, yes, the file sizes in both apps had become bloated but are now fine. Some funny things happened to some buttons when I copied from the original lc file into the new stack generated in v7.0.5, such as borders disappearing from buttons and them being set to disabled. Not a big deal to fix. I just need to test some more to see if any scripts have gone strange. I only found one case in the other app.
The joys of development!
Bye,
Hilton.
I checked the original app I wrote (not the one referred to before) and whilst it was slow in the IDE about 4secs to change a card it was not impossible, I noticed that the lc file was 20Mb.
I followed the previous procedure and the file size reduced to 1.2mb and the speed is pretty good now. So, yes, the file sizes in both apps had become bloated but are now fine. Some funny things happened to some buttons when I copied from the original lc file into the new stack generated in v7.0.5, such as borders disappearing from buttons and them being set to disabled. Not a big deal to fix. I just need to test some more to see if any scripts have gone strange. I only found one case in the other app.
The joys of development!
Bye,
Hilton.
-
- VIP Livecode Opensource Backer
- Posts: 10043
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: Speed of moving from Card to Card
When it was slow in the IDE, was the IDE's Project Browser window open? I wonder if a large number of hidden objects may be at play here, which you might not see but the Project Browser would have to create entries for when the card is opened.hilton wrote:I checked the original app I wrote (not the one referred to before) and whilst it was slow in the IDE about 4secs to change a card it was not impossible, I noticed that the lc file was 20Mb.
I followed the previous procedure and the file size reduced to 1.2mb and the speed is pretty good now.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
Re: Speed of moving from Card to Card
Richard,
Yes I always have the project manager open. Unfortunately, I am too inexperienced to comment on your idea. All I know is that everything is fast and working well. As I said apart from a few corruptions which I was able to locate and fix all is well in both my apps and running fast on both Windows and Android.
Hilton.
Yes I always have the project manager open. Unfortunately, I am too inexperienced to comment on your idea. All I know is that everything is fast and working well. As I said apart from a few corruptions which I was able to locate and fix all is well in both my apps and running fast on both Windows and Android.
Hilton.