How is it possible to increase the size of the workbench (Canvas) in the gnuradio-companino - gnuradio

I am working with Gnuradio-companion, working on a bigger project with a lot of blocks for the first time. The space on the workbench is getting scarce.
Do you know if it is possible to increase the size of the workbench?

Starting with GNU Radio 3.8, this is no longer necessary: the canvas auto-adjusts its size, and you can zoom around in it (usually, using ctrl+scroll wheel).
So, if this is a problem you're encountering, you're using the End-Of-Life GNU Radio 3.7 release series (or older). You should not be doing that. It's time to upgrade your GNU Radio.
To preserve the old answer:
Double-Click on the "Options" block and adjust the "Canvas Size" (it's width, height in pixels).
Another good approach to keep your flow graph manageable is to take groups of blocks and put them into "hier" blocks (select connected blocks, right click, more, Create hier); use "Pad Sinks" and "Pad Sources" to create in- and outputs for your new hier block, and use that hier block in place of the bunch of blocks, to keep your flow graph tidy!

Related

What parameter in Cytoscape determines the stacking order of edge rendering?

I have created a cytoscape network with a number of crossing and re-crossing edges. It is meant to do this, and I don't wish to reduce the amount of crossing that is occurring.
I would, however, like to be able to determine which edges are on "top" and which are in "back" - in the same way that you would "bring to front" or "send to back" in Powerpoint or Photoshop or any of numerous display programs.
Which style parameter or similar value is used to determine rendering order of edges? Note that I am referring to the edge line itself, and not some annotation.
Thanks much.
Unfortunately, that isn't available in the current release, but Cytoscape 3.9 will include that feature. If you want to try a copy of 3.9 (which isn't nearly ready for production release), you can download it at: https://cytoscape-builds.ucsd.edu/cytoscape-builds/Cytoscape-3.9.0/
-- scooter

Is it possible to use the After Effects 'Create Shapes from Vector Layer' functionality from within a script (Adobe ExtendScript)?

I am attempting to create a script for Adobe After Effects. Part of what I am attempting to accomplish will require converting layers imported from Illustrator into After Effects shape layers.
I am having trouble finding any info on how this can be accomplished in ExtendScript. Is it possible?
Any menu commands in After effects are available to extendscript, even if they're not included in the API. To invoke a command as you would with a menu you use
app.executeCommand(1234);
Where 1234 is the number of the command you want. To find this magic number there is a function
app.findMenuCommandId("Full text of command as it appears in the menu");
It's kludgy, and there's no guarantee that adobe will stay consistent with the numbers between releases, but it's all we have. More details and a list of magic numbers here

ROIs in Digital Micrograph EELSspectra behave strangely after command "EELSSubtractPowerlawBackground()" - Bug? (GMS 2.3)

When I run the script below on a DM EELS spectrum that already contains background and signal ROIs, it is ok if I don't show any images.
ImageDocument imdoc = GetFrontImageDocument()
image i0 = ImageDocumentGetImage(imdoc,0)
image subt = eelssubtractpowerlawbackground(i0,800,900)
//image irrelevant = realimage("irrelevant",4,100,100)
//showimage(irrelevant)
But if I show any image after running the background subtraction command (activate the last 2 lines for example) the pre-existing ROIs on the initial image are changed (sig disappears and bckgd is moved to the new position).
This is despite i0 being in theory a new image, not part of the initial one.
Creating copies within the script and working on them appears in any case not to solve the problem.
More surprising is that if I first make a duplicate of the initial image and run the script on that, then close the new windows and the (modified) spectrum on which the script was run, then try and duplicate the initial image, the duplicate has the modified ROIs rather than its own. A second duplicate seems to be ok. I have no idea what's going on. Grateful for any ideas.
(The problem was initially part of a much bigger script in which I need to show images, I've reduced it to the essentials here). I'm using v2.3.2.
I have tested your script on an EELS Spectrum with ROIs in GMS 2.3.3 and in GMS 3.2.2
GMS 2.3.3:
It does not seem to happen due to the ShowImage() but rather whenever the display of the image the last Background/Signal ROI was used on is refreshing its display. You get the same behavior when you run your script without the last two lines, but then click on another image (to select it) and then the spectrum again. And you get the same if you've used the background-subtraction ROI on a completely different image and then run the script. It messes up that last images' ROIs.
GMS 3.2.2: Doesn't show this. All is fine regardless what you do.
So, from these two tests I would conclude it is a bug in GMS 2.3 which has since been fixed.
The behaviour is indeed very odd, and I see nothing wrong with your code.
The bug seems to be that the command eelssubtractpowerlawbackground() messes with the settings of the last active signal-extracting ROIs, regardless on where they are placed on. It doesn't matter what the input image is. It seems to "reuse" these last ROIs.
Unfortunately, I don't know a good workaround for it.

LaTeX (Context) document size over 226in

I've been looking left, right and center but was not able to find a definitive answer as to how and whether it is possible to increase document size in LaTeX over the magic 200inch limit.
For a project I work on I need to be able to dynamically generate PDF/EPS that can be used to print on up to 32 yards long medium. The important factor is, that this print job must be seamless and contains color stripes, symbols and texts on repeat throughout the entire length.
I know that PDF 1.6+ supports a much larger document size via setting UserUnits. Is that something that can be used in LaTeX and if so, how would I go about this?

Finding a word's frame (position and size) on the screen using Cocoa or Carbon

Here's a tough one:
I need to be able to find a word's position and size (its frame) on the screen (its first occurence is enough, from there I should be able to get the next ones).
For example, I would like to be able to detect word positions in (but not limited to) Word, Excel and PowerPoint for Mac, as well as Safari and others.
The solution should be as fast as possible; I should be able to find at least 5-6 words per second and use as little CPU time as possible.
Here's what I thought of so far:
OCR in a window's screenshot / graphics context (any good Open Source framework that works on Mac OS X 10.4 and that can be used in a commercial product?). Evernote is very good at spotting words in images. I don't know if it uses a custom in-house engine or an Open Source / commercial one but that would be the kind of engine I would like to use if this is a "valid" solution. Ideally I would detect the word's frame in the active application's window (how to get the frame of another application?).
Getting some kind of "hook" on Quartz drawing of text and intercepting the location of the word when it's drawn (does not seem very feasible at first glance!).
AppleScript, but it depends a lot on what API the application offers (I don't think you can get a word's coordinates in a Word document from what I've seen) and it's slow.
... out of ideas ...
My goal is to get all the word's frames in a paragraph in the right order based on a string containing the text of the paragraph.
Thanks in advance for any hints!
As a starting place, you may want to take a look at QuickCursor's code. It retrieves text from many different applications through the AX Accessibility APIs. Now, it won't grab the pixel placement of the word, but it will at least return the NSString associated with the text in that UI element. Of course this means that the app in question has to support these APIs; I don't know if the MS Office suite would. In addition, it only supports editable elements, so an un-editable webpage in Safari won't work either. But it may give you a starting point for some ideas.
Take a look at the QCUIElement.{m,h}, and then the implementation in the QCAppDelegate.m (beginQuickCursorEdit:)... the implementation of his abstracted QCUIElement seems to be as simple as:
QCUIElement *focusedElement = [QCUIElement focusedElement];
id value = focusedElement.value;
Edit: Aha! Check out the Accessibility Inspector Sample code: UIElementInspector. It can actually get the AXPosition of elements on a page. Now, it's not word-by-word, but we're getting closer. It'll tell you the x,y placement of a textblock, as well as the words contained in the textblock.
This is possible, but very hard to get working reliably. You can play with Spell Catcher's Direct Connect feature to see an example.