On 9/24/09 6:35 PM, in article C6E16C5A.77B8%dru@summitprojects.com, "Dru Kepple" dru@summitprojects.com wrote:

Here's some stripped down code that works:

TextMate::UI.dialog(:nib => nib, :parameters => {}, :center => true) do |dialog| dialog.parameters = {'username' => "moo"} dialog.wait_for_input do |params| puts params["username"] end end

But then I go to try and actually use something with my params hash, like putting it into a variable declared earlier:

username = "" TextMate::UI.dialog(:nib => nib, :parameters => {}, :center => true) do |dialog| dialog.parameters = {'username' => "moo"} dialog.wait_for_input do |params| username = params["username"] end end puts username

Read the docs. :) Okay, there aren't really docs, but there is a very helpful comment explaining how to use wait_for_input:

# wait for the user to press a button (with performButtonClick: or returnArguments: action) # or the close box. Returns a dictionary containing the return argument values. # If a block is given, wait_for_input will pass the return arguments to the block # in a continuous loop. The block must return true to continue the loop, false to break out of it.

So, you're blocking because that's what the block does. It's just doing what you told it to do. But for your purposes, you don't need a block. Just capture the result of the call. So, for example (using a built-in nib example):

require "#{ENV['TM_SUPPORT_PATH']}/lib/ui" nib = "#{ENV['TM_SUPPORT_PATH']}/nibs/RequestString.nib" username = "" TextMate::UI.dialog(:nib => nib, :parameters => {}, :center => true) do |dialog| dialog.parameters = {'string' => "Matt"} username = dialog.wait_for_input end puts username["returnArgument"]

Hope that gives you enough to move forward... m.

I'm actually have the same issue. Once the .nib gets loaded in TextMate, everything locks up. I can move the custom window around, but I can't type into the input boxes, close the window, or click any of the buttons.

The change that that was mentioned—removing the block from the dialog.wait_for_input—did not have any effect. I have, however, figured out that if I change my bundle command's output from "Replace Selected Text" to "Show As HTML", the window loads and works properly. Having that output type isn't functional for what I'm trying to do, though.

Is having "Show As HTML" as the bundle command output a requirement when using TextMate::UI.dialog to load a custom .nib?

Jeff

drukepple wrote:

I have a question about UI.dialog and/or some general Ruby usage. I apologize for asking about Ruby stuff here, but this particular problem seems tied directly to the use of UI.dialog, although I'm pretty sure the issue is actually a Ruby one on my part (I've been fine Googling for other Ruby issues, but this one seems pretty niche).

Here's some stripped down code that works:

TextMate::UI.dialog(:nib => nib, :parameters => {}, :center => true) do |dialog| dialog.parameters = {'username' => "moo"} dialog.wait_for_input do |params| puts params["username"] end end

But then I go to try and actually use something with my params hash, like putting it into a variable declared earlier:

username = "" TextMate::UI.dialog(:nib => nib, :parameters => {}, :center => true) do |dialog| dialog.parameters = {'username' => "moo"} dialog.wait_for_input do |params| username = params["username"] end end puts username

Now I get a task that seems to hang, which when forced to quit will report the following error in Console:

TextMate[13634] *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection or ports are invalid

Really don't know what to do with this. Sorry, I'm not good enough at either TextMate's extra features, nor at Ruby. I'm sure this is just a combination of both of those deficiencies.

Thanks, Dru

---

textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate