I have worked on an app for a few months, and did not compile to a standalone until today. I have discovered a few bugs, and any help would be very much appreciated.
Problem 1-- The ask and answer dialogue boxes seem to have inherited a giant font for the buttons and the response field. I cannot figure out what to do about this as there do not seem to be any settings that control these things.
Problem 2 -- I allow the user to print to pdfs. It does not work properly in the compiled version. Cannot figure out what the difference is.
Thank you!!!
Issues with Compiling
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Re: Issues with Compiling
Hi.
Problem 1: Never heard of such a thing. I cannot imagine what is going on, unless you have explicitly hacked these two dialogs (they are only stacks, after all). Others may chime in. But if you make a brand new stack with a short handler that invokes either dialog, save it, and make a standalone, does it also appear that way?
Problem 2: Did you include the PDFprinter library?
Craig
Problem 1: Never heard of such a thing. I cannot imagine what is going on, unless you have explicitly hacked these two dialogs (they are only stacks, after all). Others may chime in. But if you make a brand new stack with a short handler that invokes either dialog, save it, and make a standalone, does it also appear that way?
Problem 2: Did you include the PDFprinter library?
Craig
Re: Issues with Compiling
So your post led me to discover that I can actually "hack" the answer and ask dialogue boxes. This potentially could solve the problem... except that changes do not seem to change. The ask and answer stacks remain unchanged when I leave and restart LiveCode. I have checked and the cantModify is false, so what else do I do?
By the way, you can see the problem I am talking about here:
https://drive.google.com/file/d/1pOOynf ... sp=sharing
https://drive.google.com/file/d/1Wt9VO7 ... sp=sharing
Any help would be most appreciated!
By the way, you can see the problem I am talking about here:
https://drive.google.com/file/d/1pOOynf ... sp=sharing
https://drive.google.com/file/d/1Wt9VO7 ... sp=sharing
Any help would be most appreciated!
-
- Livecode Opensource Backer
- Posts: 10099
- Joined: Fri Feb 19, 2010 10:17 am
Re: Issues with Compiling
I wonder if you have not set the textSize to something big either in the stack or the card which those dialogues inherit?
Mind you, I had some fun this way:
Mind you, I had some fun this way:
Code: Select all
on mouseUp
set the textSize of fld id 1119 of stack "Ask Dialog" to 24
set the textSize of fld id 1006 of stack "Ask Dialog" to 24
ask "Who's afraid of Virginia Woolf?"
end mouseUp
Re: Issues with Compiling
Thank you!
So, I don't think it is inheriting the value because the size problem only appears in the stand alone version. I think it is somehow using the default Windows System font.
In any case, the posts here gave me an idea which worked. I created a top level procedure that changes the textSize of the two dialogue boxes and then called on this procedure each time I open a substack. The key was to realize that the dialogue boxes are stacks that can be played with. I still don't get why, then, I can't make changes to the stacks, but this workaround works well, so no big deal.
Next challenge-- figuring out how to package a completed app so it can be sent. But I'll start a new thread for that.
I appreciate your help.
So, I don't think it is inheriting the value because the size problem only appears in the stand alone version. I think it is somehow using the default Windows System font.
In any case, the posts here gave me an idea which worked. I created a top level procedure that changes the textSize of the two dialogue boxes and then called on this procedure each time I open a substack. The key was to realize that the dialogue boxes are stacks that can be played with. I still don't get why, then, I can't make changes to the stacks, but this workaround works well, so no big deal.
Next challenge-- figuring out how to package a completed app so it can be sent. But I'll start a new thread for that.
I appreciate your help.