Schmye-Bubbula

  • Smile Score: +16
  • Posts: 1
  • Downloads: 68
Your MacUpdate.com profile avatar
About Me
Member Type I am a Free member
Visit Stats
Last Visit Today Member Since Dec 11, 2007

Schmye-Bubbula's Recent Posts

SkimSkimComment
Schmye-Bubbula
+0

A couple of years ago I begged the Skim developer to add a menu item & command key to toggle between fit-page-height-to-window & fit-page-width-to-window, something this presbyope need umpteen times a day. But of course, like most programmers, he put his convenience ahead of usability, functionality & user-friendliness and insisted that he "didn't want to add too many command keys that make an app confusing to the user." So that left us with the user-hostile machinations of having to make sure PDF > Automatically Resize was enabled, then switch between PDF > PDF Display > Single Page & Single Page Continuous. Grrrr!! So I wrote this AppleScript to do it, which can be assigned a command key to execute it in Keyboard Maestro, QuicKeys, FastScripts, etc. (The version of Keyboard Maestro that will run on Snow Leopard doesn't have the ability to check for menus with checkmarks.) For this AppleScript to work, you have to check the checkbox for "Enable access for assistive devices in System Preference > Universal Access. tell application "System Events" tell process "Skim" tell menu bar 1 tell menu 1 of menu bar item "PDF" tell menu item "Automatically Resize" set menuChecked to value of attribute "AXMenuItemMarkChar" try if menuChecked = "✓" then set menuChecked to true end if on error set menuChecked to false end try end tell if menuChecked = false then pick menu item "Automatically Resize" tell menu 1 of menu item "PDF Display" tell menu item "Single Page" set menuChecked to value of attribute "AXMenuItemMarkChar" try if menuChecked = "✓" then set menuChecked to true end if on error set menuChecked to false end try end tell if menuChecked = true then pick menu item "Single Page Continuous" else pick menu item "Single Page" end if end tell end tell end tell end tell end tell

Reply2 replies
Version 1.4.8
Schmye-Bubbula
+0

Oh drat, it won't let me edit! Grammar edit: "...something this presbyope needs umpteen..." And I forgot to mention that QuicKeys seems to have major problems selecting menus in Snow Leopard, at least in mine (even with Unsanity APE disabled).

Schmye-Bubbula
+0

Another grammar edit — unmatched quotation marks: "...you have to check the checkbox for 'Enable access for assistive devices' in System Preference > Universal Access."

PopClipPopClipComment
Schmye-Bubbula
+0

I couldn't get PopClip to come up on any selected text in any Tweet at Twitter.com with Firefox 28.0, and the PopClip developer, Nick Moore, kindly responded by email to my inquiry with the solution: • Begin selecting the text. • Before releasing the mouse button, press Caps Lock. • "Learn" will appear as sole PopClick bar item; click! Voila!

Reply0 replies
Version 1.4.10
PopClipPopClipComment
Schmye-Bubbula
+0

Is there a way I can add thesaurus.com to its sister site, dictionary.reference.com, which is used in the Online Dictionary? There is a procedure involving the shift key for adding a new search engine as described here: http://docs.pilotmoon.com/article/38-how-to-change-the-search-engine ...but I couldn't get it to work trying to add my thesaurus site to the dictionary site. Maybe I was abusing the process and it *won't* work with anything other than the Online Dictionary. In any event, I sure would like a Theaurus.com extension! Any suggestions?

Reply3 replies
Version 1.4.10
Schmye-Bubbula
+0

Oh drat, can't edit my post. I meant to say above, "Maybe I was abusing the process and it *won't* work with anything other than the search engine."

Schmye-Bubbula
+0

OK, I was able to add thesaurus.com as the shift-key second SEARCH ENGINE (but not as a shift-key alternative to the Online Dictionary extension): • I went to thesaurus.com for a sample word: http://thesaurus.com/browse/PopClip ...to obtain the URL in my web browser's address bar. • I substituted "***" for the the lookup word: http://thesaurus.com/browse/*** • I selected that URL in the address bar and invoked PopClip. • I shift-clicked "Set Search Engine" • Now when I select any word and shift-click PopClip's magnifying glass icon ("Search"), it gets looked-up at thesaurus.com. memo: The PopClip page to download the Online Dictionary extension is here: https://pilotmoon.com/popclip/extensions/page/OnlineDictionary ...and it lists all the different dictionary websites it supports, but IT DOESN'T TELL HOW TO CHANGE TO THOSE OTHER DICTIONARY WEBSITES! memo #2: The "Change PopClip's Search Engine" procedure is here: http://docs.pilotmoon.com/article/38-how-to-change-the-search-engine

Schmye-Bubbula
+1

OK, I finally found the place to choose among the different dictionary websites that the Online Dictionary extension supports (or any other extension with options): • Go to the PopClip menu in your menu bar. • Select the "Actions" icon (the third one with a puzzle piece icon). • Click the pencil icon at the very bottom of the list (the one that lets you drag to change the order of extensions as they appear in the PopClip bar). • That list now in edit mode also lets you set options for extensions that offer them: Click the sprocket icon next to Online Dictionary to select the dictionary website you want. Voila! (I should have known that!)

Schmye-Bubbula
+0

Version 2.11 came with "ScriptSaver 64-bit.saver" but v3.0 apparently is only 32-bit, so I have to set System Preferences to run in 32-bit with Finder Get info to be able to even configure v3.0 at all. Anyone know why a 64-bit version didn't come with v3.0?

Reply0 replies
Version 3.0
NoSleepNoSleepComment
Schmye-Bubbula
+0

> Requirements: Mac OS X 10.4.4 > and above Won't launch in 10.5.8; big cross in Finder icon.

Reply1 reply
Version 1.0.3
Schmye-Bubbula
+0

MacUpdate-Jess, perhaps half of all of MacUpdate listings have the system requirements wrong. It's so bad that I routinely have to visit the developers' websites because MacUpdate cannot be trusted. It matters not to me whether MacUpdate or the developer is responsible for getting the system requirements right; in any event, MacUpdate needs to impose stringent requirements on developers on getting it right or else they won't be allowed to post!!!!!!!!!!!!!!!!!!!!!!!!!!!!

SkypeSkypeReview
Schmye-Bubbula
+1

The latest version of Skype I can get to launch under Mac OS X 10.5.8 (which the Skype website says is the minimum requirement) is 6.0.60.2968. It's been this was every version since. Can anyone else get a newer version to work with 10.5.8?

Reply0 replies
Version 6.3.60.602
Schmye-Bubbula
+2

I can't glean from the description or from the publisher's website whether this thing will actually remove the malware, or only check for it.

Reply0 replies
Version 2.0.4
Schmye-Bubbula
+1

(Cross-posted from the FreeMemory Pro listing) Completely failed memory management in Mac OSuX "...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly. "I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...." http://dywypi.org/2012/02/back-on-linux.html

Reply4 replies
Version 1.6.1
Schmye-Bubbula
+0

Um, yes. It doesn't do what the developer docs says it does, just as described in link. I've observed it myself. Yes, inactive decreases as well as increases over time, but immaterial to the fact that inactive still gets paged to disk — doesn't matter whether it's "only" modified inactive; *no* inactive should (defeats the purpose!). Watch the swap files pile up!... If it's a scam, then why does my excruciating sluggishness go away when running FreeMemory-type utilities (or purge in Terminal)? Without them, I'd have to go back to rebooting every time this happens.

Schmye-Bubbula
+0

Yes, I'm sure. I've personally observed the undesirable behavior at least as far back as 10.4 Tiger.... Inactive should *never* be paged to disk, no matter what TheWormyFruit™'s docs say; to repeat, it defeats the purpose and the thrashing unnecessarily slows down the Mac.... Linux & other Unix-type OS apparently don't do this for the most part, it's all Apple arrogance... Some of the heavy-lifting things you described you do themselves may be purging inactive as you use them, similar to what FreeMemory-type utilities or repairing permissions do.... Nevertheless, it's not consistent & many Macs don't overtly experience it — sometimes there seems no rhyme or reason to it.... In any event, the acid test is that when one *does* chronically experience it, and purging inactive by any means (or rebooting to do so) restores robustness, I'm going to keep doing it, so I can get some work done instead of fighting the goddamned computer.

Schmye-Bubbula
+0

tavas, if you read through this thread carefully, you will see that your experience falls completely in accord with the symptoms as described: If you don't regularly bump the inactive memory red line, or if you run heavy duty RAM-intensive apps that in process invoke the native memory management routines which effectively do what manually running the Terminal "purge" command does, then you will not get the chronic spinning beach balls or virtual memory scratch files piling up. This problem recently has been getting more widespread attention (although it harkens back years), such as over on Macintouch.com: http://www.macintouch.com/readerreports/lion/topic4948-015.html ...and in "Something is Deeply Broken in OS X Memory Management": http://workstuff.tumblr.com/post/20464780085/something-is-deeply-broken-in-os-x-memory-management I think that even Nontroppo, who has had a long presence on this forum as a distinguished Mac service consultant, must slowly be coming to the realization that we have a real problem here.

Schmye-Bubbula
+0

Here's a fairly recent post that includes a YouTube video demonstrating one way to recapitulate the offending behavior on demand from over on the Mac OS X Hints Forums in the thread, "OS X prefers swapping over clearing inactive memory?" http://hintsforums.macworld.com/showpost.php?p=679267&postcount=6

Schmye-Bubbula
+0

Completely failed memory management in Mac OSuX "...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly. "I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...." http://dywypi.org/2012/02/back-on-linux.html

Reply1 reply
Version 1.6
Schmye-Bubbula
+0

I disagree. (See my remarks for the non-Pro version http://www.macupdate.com/app/mac/40342/freememory )

Schmye-Bubbula
+7

In Script Editor.app, enter the AppleScript command: choose color ...and save as an Application bundle.

Reply0 replies
Version 1.0.1