Your comments
You should be able to add clip="yes" to your "all-encompassing container panel" and any child should crop to the bounds of your cornerradius.
12 years ago
Ok let's see if I can't answer these:
Does downloading an image (using download) use the full memory of the image or does it stream into storage?
Not sure what you mean by stream into storage, but the download tag does store the full version of the image in the applications folder of the app, so you can retrieve it and use it at anytime within the app.
When loading an image, does suppress=yes load the image into memory then unload it?
The image tag suppress attribute tells the engine to reserve the geometry for the image, but to not actually load the image content. You can then use the load tag action to bring in the content whenever you want.
Does assigning the property suppress=yes unload an image if it is already loaded?
Suppress is not an assignable object property.
Does changing the source property on an image unload the previous image and load the new image? or should you use unload, then load?
If you assign a new image to the same tag, it will unload the old image and replace it with the new image. However if the image is not coming from a URL, then it is still stored in the app even if it is not loaded into memory, it still takes up space in the project.
If you create an image using the URL parameter and then later assign a new image using source, does the memory get released for the URL image?
Only the current source/url will take the memory hit and you can't have both types on the same image tag. You would need to use two image tags to achieve this scenario.
Does downloading an image (using download) use the full memory of the image or does it stream into storage?
Not sure what you mean by stream into storage, but the download tag does store the full version of the image in the applications folder of the app, so you can retrieve it and use it at anytime within the app.
When loading an image, does suppress=yes load the image into memory then unload it?
The image tag suppress attribute tells the engine to reserve the geometry for the image, but to not actually load the image content. You can then use the load tag action to bring in the content whenever you want.
Does assigning the property suppress=yes unload an image if it is already loaded?
Suppress is not an assignable object property.
Does changing the source property on an image unload the previous image and load the new image? or should you use unload, then load?
If you assign a new image to the same tag, it will unload the old image and replace it with the new image. However if the image is not coming from a URL, then it is still stored in the app even if it is not loaded into memory, it still takes up space in the project.
If you create an image using the URL parameter and then later assign a new image using source, does the memory get released for the URL image?
Only the current source/url will take the memory hit and you can't have both types on the same image tag. You would need to use two image tags to achieve this scenario.
Greg,
Sorry about that! We are waiting for the new fusebox to get approved by apple so in the meantime you will need to create an Ad-Hoc build for twitter 1.1 to work. In the meantime you can still switch it back to 1 for testing in fusebox, but Twitter could kill the old API at any time so don't rely on it.
Sorry about that! We are waiting for the new fusebox to get approved by apple so in the meantime you will need to create an Ad-Hoc build for twitter 1.1 to work. In the meantime you can still switch it back to 1 for testing in fusebox, but Twitter could kill the old API at any time so don't rely on it.
CSnapp1,
Currently unless you are using the dismiss button that is native on the keyboard (ipad only) then you do need to identify a target for the textfield that is using the keyboard to dismiss it. You are right on track with the variable solution b/c then you only need a single action to dismiss several textfields.
You can add an onclick="keyboard-off" trigger to other objects that are on the screen when your keyboard is open that will trigger the keyboard to close as long as the target is correct. So it might make sense to move your textfields in a reusable class that can share a single object variable.
Currently unless you are using the dismiss button that is native on the keyboard (ipad only) then you do need to identify a target for the textfield that is using the keyboard to dismiss it. You are right on track with the variable solution b/c then you only need a single action to dismiss several textfields.
You can add an onclick="keyboard-off" trigger to other objects that are on the screen when your keyboard is open that will trigger the keyboard to close as long as the target is correct. So it might make sense to move your textfields in a reusable class that can share a single object variable.
Cindy,
In truth the calculator example we built to demonstrate the concepts of variables and if statements, so it is admittedly not the most advanced wire from a calculator standpoint.
I would need to spend some time updating the tutorial to accomodate for this scenario. It would require you to reevaluate the if statements that occur on the 'operate' action and allow an action similar to 'total' perform an eval statement that captures the [object:ENTRY.text] and saves it as a variable at the correct time and place to use for a new calculation for a new entry.
In truth the calculator example we built to demonstrate the concepts of variables and if statements, so it is admittedly not the most advanced wire from a calculator standpoint.
I would need to spend some time updating the tutorial to accomodate for this scenario. It would require you to reevaluate the if statements that occur on the 'operate' action and allow an action similar to 'total' perform an eval statement that captures the [object:ENTRY.text] and saves it as a variable at the correct time and place to use for a new calculation for a new entry.
Perfect Steve, forgive me for not suggesting that. I am still navigating the Parse integration possibilites.
I will keep you updated on the status of PUT as well. That would solve things.
Richard,
I tested this scenario and it does appear to be a bug. You will need to use the first solution as a workaround. I will log a bug request.
Regarding your second question, there is a global variable called [file:nameoffile] that can return a yes or a no depending on whether the file is stored in the resource bundle or not. This could be useful as you can check if the last file was downloaded correctly.
I tested this scenario and it does appear to be a bug. You will need to use the first solution as a workaround. I will log a bug request.
Regarding your second question, there is a global variable called [file:nameoffile] that can return a yes or a no depending on whether the file is stored in the resource bundle or not. This could be useful as you can check if the last file was downloaded correctly.
What specific scenario are you trying to accomplish? Does it make sense to delete and re-add the object using GET/POST?
- If I want to use styles in my subwire, should I put them in the subwire or the superwire? Will one or both work? (And if both, are there any limitations or advantages?)
Subwires can only initiate the styles that are placed directly in that wire. So you would need to replicate any similar styles for each wire file.
- When I'm pathing from a subwire, do I path relative to the subwire or the superwire?
When you path you are pathing relative from the include tag that initiates the subwire to the ROOT of the main.wire.
- Why must I specify a target to play superwire actions? (Can you have multiple or nested superwires?) And is there an option other than backwards pathing to do so? (Like an alias that lives in the superwire or something?)
We have been making strides here. Try not adding a target to your play action when it contains superwire="yes" and it should find the main.wire.
Subwires can play actions inside of the main.wire, but not the other way around.
Subwires can only initiate the styles that are placed directly in that wire. So you would need to replicate any similar styles for each wire file.
- When I'm pathing from a subwire, do I path relative to the subwire or the superwire?
When you path you are pathing relative from the include tag that initiates the subwire to the ROOT of the main.wire.
- Why must I specify a target to play superwire actions? (Can you have multiple or nested superwires?) And is there an option other than backwards pathing to do so? (Like an alias that lives in the superwire or something?)
We have been making strides here. Try not adding a target to your play action when it contains superwire="yes" and it should find the main.wire.
Subwires can play actions inside of the main.wire, but not the other way around.
Customer support service by UserEcho
