Strange behavior when deleting text in an email.

When composing emails I have noticed that if I make a mistake and delete some text it behaves strangely. This only happens if the text deleted is at the end of the message. On deleting the text I am then left with a small highlighted area (like when you have used your cursor to select an area). If I then try to continue typing it types a few letters and then stops and the new letters typed just go over and over in the same cursor spot. This is difficult to describe so i hope I have made sense but it is extremely frustrating and I was wondering if anyone else was having the same problem of if it is a known bug??? If anyone knows, please could they let me know :-)
Thanks
P.S. I'm on an iMac using 10.7.3

Thanks for the info sanjapet.
1) I just trashed the Preferences
com.apple.mail.plist
com.apple.mail.plist.lockfile
2) then reboot. It is still misbehaving in texts in Apple Mail. For example i select a whole paragraph but only some words are highlighted. Here is a sample
http://www.pixentral.com/show.php?pi...rYnikzXiYS5Ir0
very annoying indeed.
3) Now i go to Preferences and
com.apple.mail.plist
com.apple.mail.plist.lockfile
are not there any more. I thought Apple Mail will restored them automatically. Isn't that right?
Best,

Similar Messages

Strange behavior when deleting XML nodes

I am developing a thermocouple product builder for a client. I have an XML file that looks like this:
<thermocouple>
<step id="step1">
    <property name="CALIBRATION">
        <option code="K">TYPE-K (CHROMEL-ALUMEL)</option>
        <option code="J">TYPE-J (IRON-CONSTANTAN)</option>
        <option code="N">TYPE-N (NICROSIL-NISIL)</option>
        <option code="T">TYPE-T (COPPER-CONSTANTAN)</option>
        <option code="E">TYPE-E (CHROMEL-CONSTANTAN)</option>
        <option code="S">TYPE-S (PLATINUM-PLAT 10% RH)</option>
        <option code="R">TYPE-R (PLATINUM-PLAT 13% RH)</option>
        <option code="B">TYPE-B (PLAT 6% RH-PLAT 30% RH)</option>
        <option code="C">TYPE-C (TUNG 5% RE-TUNG 26% RE)</option>
    </property>
</step>
<step id="step2">
    <property name="MATERIAL">
        <option code="1" ncw="JEC">INCONEL 600</option>
        <option code="2" ncw="NSRBC">304 STAINLESS STEEL</option>
        <option code="3" ncw="NSRBC">316 STAINLESS STEEL</option>
        <option code="4" ncw="NSRBC">310 STAINLESS STEEL</option>
        <option code="5" ncw="NSRBC">446 STAINLESS STEEL</option>
        <option code="6" ncw="JNESRBC">NICROBELL-B</option>
        <option code="7" ncw="JNESRBC">NICROBELL-C</option>
        <option code="8" ncw="JNESRBC">HASTELLOY-X</option>
        <option code="9" ncw="KJNE">TANTALUM</option>
        <option code="22" ncw="JNE">ALUMINA</option>
        <option code="33">MULLITE</option>
        <option code="44" ncw="KJNE">MOLYBDENUM</option>
    </property>
</step>...etc.
</thermocouple>
As each step is loaded, an XMLList is culled from the XML file for that step, and then that XMLList acts as the data provider for a combobox. When the first step has been completed, a flag called "calCode" is set using the @code attribute from the step 1 data.
Steps 2 through 4 have some options that will not work with certain calibration types from step 1. So I added another attribute to those options, @ncw. This stands for "not compatible with". If a calibration code exists inside a certain option's @ncw attribute, that means that option should not be included in the XMLList that is the data provider. Here's the code I wrote to do this:
myXml = thermoData.lastResult.step.(@id==myStep).property.option ; /* Initialize the XMLList */
            if(calCode) { /* If the calCode flag is set */
                for(var i:uint=0;i<myXml.length();i++) { /* For each item in the XMLList */
                    if(myXml.@ncw[i]) { /* If the @ncw attribute exists in the current item */
                        if(myXml.@ncw[i].match(calCode)!=null) { /* If the calCode is found in the value of the @ncw attribute */
                            delete myXml[i]; /* Delete the current item */
Here's where things get screwy. If I choose Type C in the first step, the resulting XMLList for step 2 should be very small because that calibration type is only compatible with a few materials. It should look like this:
<option code="9" ncw="KJNE">TANTALUM</option>
<option code="22" ncw="JNE">ALUMINA</option>
<option code="33">MULLITE</option>
<option code="44" ncw="KJNE">MOLYBDENUM</option>
However, when I test it, it looks like this:
<option code="2" ncw="NSRBC">304 STAINLESS STEEL</option>
<option code="4" ncw="NSRBC">310 STAINLESS STEEL</option>
<option code="6" ncw="JNESRBC">NICROBELL-B</option>
<option code="8" ncw="JNESRBC">HASTELLOY-X</option>
<option code="9" ncw="KJNE">TANTALUM</option>
<option code="22" ncw="JNE">ALUMINA</option>
<option code="33">MULLITE</option>
<option code="44" ncw="KJNE">MOLYBDENUM</option>
It seems to be deleting every other item in the XMLList where the calCode exists in the @ncw attribute, instead of every item. Does anyone know why? I am only an intermediate ActionScript programmer, and this is my first Flex project ever, so I'm totally willing to accept that I could have made a huge mistake somewhere. I can post the entire source code if you want to look it over... it's pretty long and I'm rubbish at commenting. Thanks!

I figured it out. This is probably a pretty amateur mistake. By checking each node in turn and deleting it if there is a match, I'm unintentionally changing the index number of each subsequent node. So if myXml[1] gets deleted, all the other nodes have their indices reduced by one, but the loop counter continues to increment, so the node that was 2 is now 1, and it never gets checked. I think instead of deleting nodes I need to treat the master XMLList as a source and move the non-matching nodes to a duplidate list that will then act as the data provider.

Strange behavior when I try to match a mpeg2 video with the menu size image

hello all,
got a strange behavior when I try to match a mpeg2 video with the menu size image,
menu size is 1920 x 1080 (photoshop file)
mpeg2 video 1920 x 1080 (1second 19 frames)
the idea is to go from the menu link to the next sub menu with a video as transition, using the same image on the video as the menu and then zooming in (in my case through a door) to end up after the zoom in the next level menu.
I try to achieve a smooth change from the first play menu picture to the video image into the next level menu picture,
everything works good but when I watch it on the preview mode on the left and right side of the video it shows a black bar at least 15 to 25 pixel wide, that means the video image appears smaller and it causes a little jump what is preety disturbing and can not be sold as a professional work.
why encore treats the video size and picture differently?
it's gratful appreciated if somebody who got experience in a transition I mentioned obove posting any solution,
thankl you all

Hi all
I'm having a very similar problem with Encore. My menu items are distorting (a minor but infuriating squashing top and bottom) when previewed.
Using Encore,PS,AE CS4
DVD format SD PAL DV widescreen
I created 3 menu frameworks and 3 video transistions to link them in AE. On the final frame of each transistion in AE I saved the frame with Composition>Save Frame to> Photoshop Layers. In PS i added the button functionality and saved.
In Encore I use Dynamic link to import AE transistions as timelines and imported each PS menu twice, once as "menu" and once as an asset.
When I link the timeline transistions to the menu and preview at the point the menu begins the whole image is squashed. When the next transistion is activated the image returns to its original size.
Thinking it was the use of PS that was causing the menus to distort I used the menu asset directly in the time line. Obviously no menu functionality but also no distortion. The AE transistion flowed straight into the "menu" just as I expected.
In the properties panel the menu Aspect Ratio 16:9
The AE transistions PAR is SD PALwidescreen 1.4587.
I did try the Blu Ray suggestion above but the same distortion was apparent.
Any suggestions short of squashing the video to match the menu would be welcomed.
Thanks

Strange behavior in deleting images - works on second but not first try

In Library mode, Grid view, right after importing, after I select several images with an "x" to be deleted, when I bring up the "Delete Rejected Photos" dialog, I find this strange behavior. I get the message that there are not photos marked for deletion. I then invoke the dialog again, and my photos that were marked show up, with the choices of deleting from disk or removing from the catalog. What am I likely doing wrong? I'm on WinXP Pro with LR 2.2. Thanks!
Dilip

Dilip,
I too have seen this behaviour in all versions of LR. Even when deleting a single image in the develop module. If LR is writting the preview you can't delete the file until the preview is rendered. I think it's more to do with the OS not allowing the deletion of a file being accessed than a LR bug as such.
Gordon

Time Machine - strange behavior while deleting old backups

Not sure if this is the right place, because this is actually not on Time Capsule, but on a Time Machine on an external USB drive.
In any case, I searched the web for "time machine delete old backups" and found many discussions of various aspects of this task. My objective is to clean up a partition on a the external drive that I no longer use for active TM backups, but to retain a small set of backups in case I need to go back to them. The partition now has other uses and I need the space. My main TM backup is now on a separate Time Capsule.
So again my objective is not to remove all backups, but just most of them.
It appears that the well-discussed procedure is the following:
Go into Time Machine.
Select the Macintosh HD.
Go back to one of the oldest backups.
Click on the Gear > click Delete Backup.
This procedure will remove one Backup at a time, and it seems to take 5 - 10 minutes for each backup.
Here is what I noticed that was "strange":
You could delete a selected backup using the above procedure.
For the first selected backup so deleted, there is a confirmation dialog with a warning message that it is not undoable.
After clicking OK on the warning message, the display backs up to the "Present" backup, and the administrative password is requested.
After the administrative password is entered, the backup starts but control is passed back to the user interface, and another backup can be selected to be deleted.
However, after the second backup is selected and deleted, there is no warning dialog, and no request for the administrative password. At this point the user interface is busy and nothing more can be done until the backup delete is completed. Except that the Time Machine can be exited by first pressing Escape, then Cancel on the lower left of the screen.
If the time machine is exited, there is a Delete Backups progress dialog with a progress bar for each backup so far requested. If the second backup was requested, as in the steps above, there would be two backups.
I discovered by playing around that either you had to wait within Time Machine for the deletion to complete, or alternatively exit Time Machine. While I was not sure what was going on, I kept starting one backup, then exiting Time Machine and re-entering Time Machine and requesting another delete operation. Each time after entering Time Machine, the warning/admin password sequence occurred and I was able to exit. And then immediately re-enter Time Machine and request another backup. Only by exiting and re-entering could another delete request be made.
When out of Time Machine, I thus saw the Delete Backups dialog with any number of concurrent "Delete One Backup" progress bars.
Because of the nature of the hard links used to indicate backups, I was wondering if these multiple delete operations could possibly be hung in a deadly embrace, so I decided to only do one at a time. Some further study to see if the multiple delete operations were all able to complete would be needed to know if this would be a good way to "queue up" multiple delete requests.
Bottom line: seems like kind of an odd implementation. Would be really nice if you could select many (say 30) individual backups and delete them all at once, rather than taking 5 - 10 minutes each. Again, this is because I am trying to reclaim disk space, but not delete all the backups from a Time Machine backup set that is not in active use.
Also, the method of "queuing up" backup delete requests is kind of odd, but seems to work, with the proviso that I have not yet confirmed that doing more than one at a time actually works.

Heinz-G?uenter Arnold wrote:
since the upgrade to SL it seem that Time Machine has problems to completely remove old backups completely. The "removed" backups do not show up in Time Machine anymore, but the backup folders and part of their contents can still be seen in Finder.
Hi, and welcome to the forums.
That happens occasionally, in both Leopard and Snow Leopard, sometimes after something was deleted from the Finder, but also after an abnormal shutdown or improper disconnection of the TM disk.
Run a +*Repair Disk+* on it via Disk Utility, in your Applications/Utilities folder. If it finds errors, but can't fix them all, run it again (and again) until it either fixes them all, or can't fix any more.

Strange issue when scaling text

Hi,
I'm using inDesign CS6 and there's a strange issue when rescaling a text with overflow to 200%:
As you can see, the fourth paragraph doesn't change its font size, even if it has exactly the same configuration. This happens apparently randomly to some paragraphs, or even lines of a paragraph in some cases.
The weirdest thing is that I have tried the same action with the same .indd file in other computers (another Mac and a Windows one, both CS6) and it scales properly all paragraphs. So I checked all the preferences from one computer to the other, and even if they are the same, the scaling issue still happens.
Any hints?

See Replace Your Preferences

Warn when deleting text anchors

I use hyperlink destinations to create cross references. However it happens, that I accidentally delete the created text anchors. Is it somehow possible to show a warning or something like that, when a text anchor is being deleted? Scripts would also be an option, if it's possible that way.
Thank you very much,
Jan

Sure, just use a preflight profile that checks for unresolved
cross-references.
That way, whenever you accidentally delete a hyperlink destination, the
little preflight button will turn red.

Strange behavior when compiled with Visual C++ 2005 Express Edition

I wrote a program for Berkeley DBXML 2.2.13 on Windows XP that executes a query 5 times and prints out the runtime for each execution. When I run the program using the Debug version of the libraries the queries take about the same time to execute for all 5 executions. When I run the program using the Release version of the libraries the execution time of the queries degrades significantly between each execution. One query takes 2 seconds to execute the first time and 20 to execute the last. I have tried recompiling the Release version without optimization and the strange behavior persists. I have run both the Release and Debug versions several times and gotten the same results, so I doubt it is a program running in the background that is slowing the execution.
This behavior does not happen when I compile the program under Unbuntu using g++, so I assume it is caused by some flag set in the Release version of Visual C++. Has anyone else experienced this behavior and know what flags I should or should not set?
Thanks for your time.
Lauren

Hi Lauren,
We've had users experience this before, and it seems to be a bug/"feature" of the default windows heap allocator. Please see this post for a bit more explanation and a solution:
Re: Performance Issue caused by XmlResults.next().asString();
John

When I text someone their email flashes briefly in grey?

I've had a hard time googling this one but have a picture. Basically when I text someone from my iPhone 4S the screen does something weird and very quickly the email of the person I'm texting flashes above in grey. This just started happening today. Thanks in advance :)

Turn off imessage and it should show your name on their device and not your email address.

Strange behavior when shutting down - only works once

Hi there,
I'm taking advice from around the forum to create a shutdown button for my VI. When the user sends the shutdown command, the loop stops all processes running and turns off all heaters. Then when this is complete it passes a shutdown variable to all loops allowing them to close. This seems to work perfectly once, but when I hit run again and test it again, it fails. If I abort the VI and restart again, the shutdown works. I can't quite figure out what the behavior is doing here.
Attached is my program, it's a little messy but everything works, and it has to be added to by someone who isn't me, so I tried to keep everything clear and seperate. If anyone's got any ideas as to what is causing this strange behavior I'd love to hear it.
Thanks,
Chris.
Attachments:
Main VI.vi ‏259 KB

First of all, your event loop should look something more like this. Otherwise you won't exit the loop until another event comes through.
Secondly, I think you are writing to the wrong control here (this is in your timed loop). I have no clue what is in the subVI, but I don't think it should be looking at the Shutdown PB control. That control should be in it's event case. But here you are trying to cause the shutdown event, but you are writing to the wrong control.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Event Structure issue.png ‏10 KB
wrong property node.png ‏3 KB

Strange behavior when "trying" to burn a disk.

At least I think this is strange behavior, following the instructions in the help viewer, topic "Backing up your music to a CD or DVD." One thing for sure, it's not burning a disc and it ain't telling me why.
I select the playlist and click "Burn Disc"
Requests a blank disc. I insert one.
Message "checking media"
after about a minute, the disc ejects
Message "checking media" displays another 30 seconds
No other messages displayed.
What the ??? Shouldn't it at least display an error message??
Super-Drive information..... from System Profiler
MATSHITA DVD-R UJ-845C:
Firmware Revision: DPP9
Interconnect: ATAPI
Burn Support: Yes (Apple Shipped/Supported)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -RW, +R, +RW
Burn Underrun Protection CD: Yes
Burn Underrun Protection DVD: Yes
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media: No
Using Sony DVD+R discs.
Mac Mini Mac OS X (10.4.8)

Whoops, sorry, this was while burning a playlist.
I've also tried some Pleomax CD disks (Samsung), with no luck. I've tried burning directly from iTunes, and from Toast 7.
Of the types I've tried, the Sony DVD's have been the best for me. Haven't tried many types though. Maybe I can get disks one at a time until I find a brand my burner likes.
Still, isn't it strange that there is NO error message? It just quits?
Mac Mini Mac OS X (10.4.8)

Strange behavior when resizing with 'Selection Tool'

Hello,
I have a really strange issue when using selection tool to resize object. I have several rectangles stacked and grouped inside a layer. When I select one of them (either in Layer panel or with Group selection tool) and switch to 'Selection Tool (V)' to resize it, this tool behaves diferently at diferent zoom levels. Only at 200% zoom it behaves as it shoul.. With 100-150% zoom result is diferent - like there's a invisible box around selected object and I'm resizing it.. I've tried to explain the issue in attached image.. Anyone knows why is this happening?
Thanks.

- make new document, size 16383x16383px
- create rectangle any width, hight say 200px (or anything less then 320px for 5% zoom)
- select rectangle and show bounding box
- try resizing hight by stretching bounding box
- this is how same selection looks at diferent zoom levels
- same zoom level as befor, hight 100px..

Strange behavior when performing query

Hi all,
I'm getting some odd behavior when doing different kinds of queries and am hoping someone here can help out. I have a database with continuously updated PDML data (http://www.nbee.org/doku.php?id=netpdl:pdml_specification). I am opening anf querying the database from a seperate application. This appears to work fine for certain types of queries, and fails for other types with error messages that don't seem relevant. Specifically, some queries that use the attribute axis as the last leaf seem to get fouled up. Here are some example queries and the results I get:
First some queries that work:
Query: "string(collection()[1]/packet[1]/proto[1]/field[1]/@size)"
Result:
A valid number
Query: "collection()//proto[@name='geninfo']/field[@name='len']"
Result:
<field name="len" pos="0" show="64" showname="Packet Length" value="40" size="64"/>
<field name="len" pos="0" show="64" showname="Packet Length" value="40" size="64"/>
<field name="len" pos="0" show="64" showname="Packet Length" value="40" size="64"/>
Now some queries that don't work:
Query: "collection()//packet/proto/field/@size"
Result:
Output to stdout - "Transaction specified for a non-transactional database"
and an Exception with message - "Error: Invalid argument"
Query: "collection()//proto[@name='geninfo']/field[@name='len']/@name" (notice it's almost identical to above working query except with @name)
Result:
Same as above, an stdout about transactions and an exception about invalid arguments
What I find most interesting is that both errors (the one printed to stdout and the one I get in my exception) don't seem to have anything to do with the problem. I know the transactional stuff isn't messed up because the exact same code works for certain queries. I'm not sure about the "Error: Invalid argument" exception, but it's not very helpful by itself. I'm using the Java library and DBXML version 2.4.16. Anyone have any ideas what's going on?
Thanks,
Dave

As a follow-up, it appears that I just needed to wrap my attributes in the XPath string() function. For example "collection()//packet/proto/field/@size" does not work while "collection()//packet/proto/field/string(@size)" works fine.
I'm still not sure why it's spitting out an error message to stdout about transactions not being enabled when the only real error is with the query, but at least it's working now.

Strange behavior when duplicating a text layer

Hello All,
I was following a tutorial.
I created a text layer. typed in the number "2012" in white
I placed a texture in the comp.
I used the text layer as an alpha track matte
Then I duplicated the Text layer, and instead of the layer being named 2012 it automatically changed to 2013.
When I look at it as Layer Name or Source Name it was the same "2013"
So I create a new text layer and type in "0" and the layer was appropiately named 0
But when I duplicated that layer it was named 2014
When I duplicated any of the text Layers it was named the next sequencially higher number
This pattern of renaming was only broken by typing in a number where the leading digit was anther value up i.e. 4329
Then the duplicating of the text layer would start naming the with this value plus 1.
Same thing happens if you split the text layer
I think this is a bug or bad programming. this can lead to unnecessary confusion if you working on a project with number text layers and have to duplicate, many of them or many times. Or is the answer to pre compose the text layer before duplicating --- NO that has its own shotcomings.
CS5.5 on a Mac Os 10.6.8

I found a solution. Rename the Text layer by adding a space before or after the numerals. Now the duplicates are named as the written text with a suffix increased by 1 for each additional duplicated layer.

Strange behavior when pressing ENTER in a form page

Hi there
Please go to the address:
http://apex.oracle.com/pls/otn/f?p=20104:4
If you click the Create button, enter anything in the Name field and press ENTER while in the field, you will be taken back to the main page, the message Action Processed will be displayed, but no data will be inserted. If you click on the Create button though, it works fine.
Have anyone seen this? Any explanation for it? How to fix it? I could not find any reason for this behavior (the Name field is NOT an always submit page when enter pressed field type).
(btw the two pages are very simple, based on wizards without any customisation)
Thanks
Luis

i guess, trying the input form, the input text field for Name is an item 'textfield submit on enter'. But what happens is that when enter is pressed no additionally submit information is send, which is the case with buttons. Buttons call the doSubmit('<BUTTONNAME>') javascript function on click, allowing the process to run when thee are set conditionally.
Carl's answer by setting the process unconditional will also result this action will take place when another buton (without direct redirect) will fire this.).
So additionally when multple buttons and processes some new javascript kan be used to do the right submit on Enter. Example:
In Page header, or shared javascript import file create a JS function submitOnEnter
function submitOnEnter(submit,e){
var keycode;
if (window.event) keycode = window.event.keyCode;
else if (e) keycode = e.which;
else return true;
if (keycode == 13){
doSubmit(submit);
return false;
}else{
return true;
Then with you're item you define the js-event onKeyPress to call the function submitOnEnter
onkeypress="javascript:return submitOnEnter('CREATE',event);"

Strange behavior when deleting text in an email.

Similar Messages

Maybe you are looking for