I have a number of character arrays in the memory dump. I need to see what's inside them. I can't find any way to expand the array.
I use JProfiler 10.0.2, the dump is from a Java 8 JVM, obtained with jmap:
jmap -dump:format=b,file=/tmp/heap.bin <pid>
Update: is there a way to save the contents to clipboard or file?
Ahh, I see now.
Partial Answer:
The contents of array are visible in References pane when you select "Outgoing References".
Related
Is it possible to extract from PDF selected (or all) spot color to separate file (also PDF - i need to preserve vector lines)? It would be best if separation will produce file with separated spot and second file with everything except this spot.
It's certainly 'possible', though not currently by using Ghostscript. You could use the devices which currently exist to filter images, text and linework to instead check the colour space of the object and use some other criteria (i.e. 'spot colour') to decide whether to pass a marking operation on to the output device. You would need to look at the ghostpdl/devices/gdevoflt.c file, and investigate the colour representation in Ghostscript.
Ghostscript's pdfwrite device can't produce two PDF files from the same input (and I suspect most PDF consumers/editors won't be able to either), you would have to run the file twice. The reason is that the graphics state would need to be maintained separately from the colour and maintained in synch between the output files.
You need to think about a few things; what exactly do you mean by 'spot colour' ? objects specified in a /Separation colour space ? What about DeviceN ? What about colourants such as /None or /All ?
http://www.blendswap.com/blends/view/73614
I have downloaded this and want to use my own text on it using Blender (or another program). It is not used for commercial purpose. When I open it, I get no option to edit text. I tried edit external and GIMP which failed.
the .blend file is binary and can only be opened inside of Blender, When you create text objects they are displayed as objects inside blender. You should be able to find the object by using the object browser section inside blender and changing it there. You may have to recreate the text object depending on how the author did the original.
I have an issue I'm working on in which I could use advice.
I wrote a VBA program that takes one worksheet and expands each row in it to many rows on a new sheet, altering one variable in each row and appending necessary xml tags. It uses this to build up data on the second sheet which is then saved as a tab delimited file. This approach works great, and I've been using it for a while now.
I've started to get big enough data sets to hit memory issues though, so I'm thinking I need to change the process and want advice on the best approach.
My initial thought is that instead of generating a new sheet, I'll read in the input sheet and then generate an array of strings separated by tab delimiters which I'll then append directly to a text file. How do I do this fastest and without hitting memory issues? Is it better to build an array and write it line by line to the text file or to write each cell as I generate it and append the tab? Will I hit memory issues? Will saving the file partway through help?
Any suggestions or alternative approaches are much appreciated.
Imagine a managed object that has got a transient attribute of type NSTextStorage. This gets archived into a binary NSData object on save. On edit I swap the textStorage of the NSTextView so all the changes go directly into the text storage. This way I can update other managed objects that are related to certain text locations without leaving the context in an inconsistent state and other UI elements using the same text storage get updated immediately.
The trouble is that the managed object context's undoManager doesn't know what to do with the text storage on undo/redo. I think it's because the undo actions are handled by the text view.
So I was thinking I could just serialise/archive the text storage on every change and replace the text storage contents with its unarchived contents. I've tested it even with longer text documents and it's not a real bottleneck on a Mac. But how do I get the undo manager to use it ? Or is there a totally different way to get it to work.
I've put a sample project up on http://cl.ly/3B1P0r2P1i0m
I'm using a Objective-C Scripting Bridge to communicate with InDesign CS3/CS4. Unfortunately I'm stuck on Save command which appears to be existing only as a part of the standard suite and not defined again in InDesign. Because of that it looks like I can Save, Save as but not Save Copy a document. Does anyone have any idea how to proceed?
Just to shortly explain the difference between Save and Save Copy - using Save Copy the current doc doesn't change which is opposite to Save or Save as.
the only other alternative other than that which philip-regan suggests. Would be to use GUI scripting but I'm still not sure what the point would be. If you wanted to save time of not closing and reopening you could save the doc make a duplicate via the finder and continue onward in indesgn with out the close and re-open bit
I always thought the distinction between Save As and Save Copy as being more semantic than anything because all that command is really doing is performing a Save As but appending the file name with " copy" (e.g., "MyLayout.indd" becomes "MyLayout copy.indd"). Just use Save as a Save Copy alternative by giving an alternate name for the document when you save it.
Edit per OP's comments: You're right that Save Copy isn't defined in the dictionary. The only way I see around this is to mimic the command's behavior by saving to a location with a new name, closing the current-yet-renamed document, and reopening the original. Not ideal, I know, but I don't see another way around it, unless Save Copy is defined in the Javascript API, which I doubt.
Well,
since Save Copy is not defined in the scripting dictionary, the only way how to proceed is to save current document a create a copy via Finder.
If you search the header file for InDesign, these are the methods that pop up:
- (InDesignDocument *) saveTo:(id)to stationery:(BOOL)stationery versionComments:(NSString *)versionComments forceSave:(BOOL)forceSave; // Save the document
- (void) saveACopyTo:(id)to stationery:(BOOL)stationery; // Saves a copy of the document.