1 Correct answer
Okey so this is first script on this forum that does such thing! Regarding reverted coordinates they were displayed right way, so like written in binary's. I said that I changed their order but true is I had but forgot, and to your post I was sure I did so 
Now it works as it should. That's not only problem with annotations, the other order of coordinates, I noticed it also in other parts like in path(Item)s. But that's other story.
In current 13th line I changed 28 value to 12. That caused (re)m
...
Explore related tutorials & articles
24
Replies
Thanks for sharing a possible way to do it.
As my scripting skills are very limited (almost only the very basic, 
), I was hopping for a simplier solution based on action descriptor code.
I will have a look at your solution, even if it seems way too much complicated for me.
@Kukurykus
Ok, thanks for the sharing! I think I can read and understand your code (but I would have not been able to write it 
).
Eventhough if your script has some drawbacks for totaly suiting my needs, I will see if I am able to do something with your script.
I have also to find some info about the $setenv and $getenv part...
@all other contributors,
Thanks for you help.
I filled a little a lack of annotations scripts. Proabably this one is original as I haven't found any that would retrieve positions of notes. To use it (after you save it in your Presets/Scripts folder of your Photoshop, which you reopen) click any annotation there's (amongst others) to make it active and run script. It will tell you selected note exact horizontal & vertical position
function bin(v) {function anno(v) {
var wh = v.match(/(.{4})(.{4})$/)
for(pos = '', i = 1; i < wh.length; i++) {
for(var h = '', b = wh, j = 0; j < b.length; j++) {
if (b
) h += b .charCodeAt().toString(16) }
pos += eval('0x' + h) + ', '
}
return pos.slice(0, -2)
}
notes = [], v.open('r'), v.encoding = 'binary'
var arr = v.read().match(/txtA.{28}/g); v.close()
for(k = 0; k < arr.length; k++) notes.push(anno(arr
)) return notes
}
function sTT(v) {return stringIDToTypeID(v)}
function dN() {
(ref1 = new ActionReference()).putEnumerated(sTT('annotation'),
sTT('ordinal'), sTT('targetEnum'));(dsc1 = new ActionDescriptor())
.putReference(sTT('null'), ref1), executeAction(sTT('delete'), dsc1, DialogModes.NO);
}
function pHS(v) {
(ref1 = new ActionReference()).putEnumerated(sTT('historyState'),
sTT('ordinal'), sTT('previous')); (dsc1 = new ActionDescriptor()).putReference
(sTT('null'), ref1), executeAction(sTT('select'), dsc1, DialogModes.NO)
}
with(psd = new PhotoshopSaveOptions()) {
annotations = !(alphaChannels = embedColorProfile = layers = spotColors = false)
}
if ($.level = 0, documents.length) {try{
(aD = activeDocument).suspendHistory('Notes', '')
dN(), executeAction(sTT('undoEvent'))
for(m = l = 0; l < (Nn = ['N', 'n']).length; l++) {
aD.saveAs(fle = File('~/desktop/.psd'), psd, true)
if (!l || N.length > 1) eval(Nn
+ ' = bin(fle)') !l ? dN() : fle.remove()
}
pHS(); while(typeof n != 'undefined' && N
== n ) m++; alert(N ) }
catch(err) {executeAction(sTT('undoEvent')), alert('No selected annotation!')}
}
It works quite fast. Poisition is alerted after few miliseconds. I did not try it much, but it does not work slower even with 100 annotations. It reads slower really big documents or with many stuff, but I didn't focus what exactly. Still that was 2 - 3 secs. So with a 'normal' documents probably up to one second. It fails for over 8 bits depth version as I had to use other regex to match the hex chars what I was not interested to do at this moment. Test it - perhaps you find something more to be fixed.
Well played !
I'm far of fully understand the code (except that you used Jarda's solution).
After testing, I found that the script returns inverted x,y results. Tried a few things (like reversing) but unsuccessfully...
I'm also enable to separate the x from the y !!
I also found that after moving or deleting an annotation, then running the script returns wrong results ( it's like if old values was kept in memory).
Okey so this is first script on this forum that does such thing! Regarding reverted coordinates they were displayed right way, so like written in binary's. I said that I changed their order but true is I had but forgot, and to your post I was sure I did so Now it works as it should. That's not only problem with annotations, the other order of coordinates, I noticed it also in other parts like in path(Item)s. But that's other story.
In current 13th line I changed 28 value to 12. That caused (re)moved notes positions could still be read, but that happened in some not specified cases like only 1 note or some custom. Originally I used 28 value as it seemed range of binary characters can't be match of regular expresion's.
I put resultant coordinates into array. They are alerted the sama way, but with chance to match one of them by N
I tested it again. Now it works a little slower (I checked old & new script for the same document). Then it was about 225 ms, now 250). For 1*1*1 document it was 130 ms with one note, but with 100 of them it was not slower for any kind of document, however when I tried it with written annotations, many layer(Sets), channels, paths and big dimmension & resolution it was slower of course, but not much for some reason, just 350 ms ?!
Putting note vertically/horizontally under 0, that is on top/left side of document will give 4294967278, so Math.pow(256, 4)!
function bin(v) {function anno(v) {
var wh = v.match(/(.{4})(.{4})$/)
for(pos = '', i = wh.length - 1; i > 0; i--) {
for(var h = '', b = wh, j = 0; j < b.length; j++) {
if (b
) h += b .charCodeAt().toString(16) }
pos += eval('0x' + h) + ', '
}
return pos.slice(0, -2)
}
notes = [], v.open('r'), v.encoding = 'binary'
var arr = v.read().match(/txtA.{12}/g); v.close()
for(k = 0; k < arr.length; k++) notes.push(anno(arr
)) return notes
}
function sTT(v) {return stringIDToTypeID(v)} function uN() {executeAction(sTT('undoEvent'))}
function dN() {
(ref1 = new ActionReference()).putEnumerated(sTT('annotation'),
sTT('ordinal'), sTT('targetEnum')); (dsc1 = new ActionDescriptor())
.putReference(sTT('null'), ref1), executeAction(sTT('delete'), dsc1, DialogModes.NO)
}
function pHS(v) {
(ref1 = new ActionReference()).putEnumerated(sTT('historyState'),
sTT('ordinal'), sTT('previous')); (dsc1 = new ActionDescriptor()).putReference
(sTT('null'), ref1), executeAction(sTT('select'), dsc1, DialogModes.NO)
}
function dHS() {
(ref1 = new ActionReference()).putProperty(sTT('historyState'),
sTT('currentHistoryState')); (dsc1 = new ActionDescriptor())
.putReference(sTT('null'), ref1), executeAction(sTT('delete'), dsc1, DialogModes.NO)
}
with(psd = new PhotoshopSaveOptions()) {
annotations = !(alphaChannels = embedColorProfile = layers = spotColors = false)
}
if ($.level = 0, documents.length) {try{
(aD = activeDocument).suspendHistory('Notes', '')
for(dN(), pHS(), m = l = 0; l < (Nn = ['N', 'n']).length; l++) {
aD.saveAs(fle = File('~/desktop/.psd'), psd, true)
if (!l || N.length > 1) eval(Nn
+ ' = bin(fle)') !l ? dN() : fle.remove()
}
dHS(); while(typeof n != 'undefined' && N
== n ) m++; alert(N .split(',')) }
catch(err) {uN(), alert('No selected annotation!')}
}
A regex I thought to use for over 8 bits depth documents wouldn't be probably different than I used. I found problem is with sole writing/reading 16 and 32 bits deepth documents with .txt file I had to use to study binary record. With annotations that would not be problem to change deepth to 8 bits for time of script work, but if we had to read binary for other goals for not only 8 bits document then I have no idea how we could do it. I wonder why for so many years noone met this problem on Adobe forums? Once Michael L Hale mentioned "out of memory" issue. I tried to do the same with .tif which can store annotations information but some lines covering bitmap data were too long comparing with psd to be read. Any ideas?
That is very useful. Honestley 1st time ever I used seek & tell was a week ago when I was writing this script. Like mentioned I tried to do the same task with .tif, but then it came impossible to read file skipping some lines using seek and tell, however I could do more than without it. I used reandch and readln as I had no idea read may be used with parameter! If that is going to work like I imagine, then I can divide longest lines into chunks. But if I guess right I have to read some exact line of some file few times, I mean opnening file to read it if I won't to avoid file was been reading endlessing. I'll try and see that works, because there must be some way to do it... It's interesting documentation I even didn't think it may exist I were in those sections now and wonder how fast I would get alerted notes coordinates if to read binaries I used strictly proper method.
You changed well to will, but still my eyes saw that word as will, because of context Only now I see that was different
You say I can read directly part of binaries by header. So if there is key word 'Anno' how to start reading binaries from/only for this section? For now before I can know it I have to read whole file, then with tell I'm getting to know position of 'Anno', and only then when I read a file second time I can use seek to point where from I want to start reading binaries. Bad way ! So question is how to start reading binaries for/from 'Anno' position without reading entire file earlier to check its position?
AdChoices