Hello Logan,

well, I have tried to do everything according to the already mentioned Post of David.
I think the names do match and I even have verified, that PopupView#parent_component= gets called.

So, I'll just post the code of my little example application:

haupt_controller.rb:

require 'popup_controller'
class HauptController < ApplicationController
  set_model 'HauptModel'
  set_view 'HauptView'
  set_close_action :exit

  def start_dialog_button_action_performed 
    @dialog = PopupController.create_instance 
    add_nested_controller(:popup, @dialog) 
    @dialog.define_handler(:ok_button_action_performed)  do
      p :ok_button_handler_called
    end
    @dialog.define_handler(:window_close)  do
      p :window_close_handler_called
    end
    p :opening_dialog
    @dialog.open
    p :dialog_closed
  end
end

haupt_view.rb:

class HauptView < ApplicationView
  set_java_class 'haupt.HauptFrame'

  nest :sub_view => :popup, :using => [:define_popup_parent, nil]

  def define_popup_parent(view, component, model, transfer)
    view.parent_component = @main_view_component
  end
end

popup_controller.rb:

class PopupController < ApplicationController
  set_model 'PopupModel'
  set_view 'PopupView'
  #set_close_action :exit
end

popup_view.rb:

include_class 'popup.PopupDialog'

class PopupView < ApplicationView
  #set_java_class 

  def create_main_view_component  # This avoids error about missing @main_view_component
    42   
  end

  def parent_component=(parent)
    @main_view_component = PopupDialog.new(parent, true)
  end
end

And the symptom I get is that everything works normal, except that clicking on ok_button has no effect, and the :window_close handler does not fire.

Thank you for your help

Sven

Sven, :window_close is going to need some more work. See add_listener in the rdoc (it has a sample near the bottom): http://monkeybars.rubyforge.org/api/classes/Monkeybars/EventHandlerRegistrationAndDispatchMixin/ClassMethods.src/M000012.html

define_handler piggybacks the implicit handler registration that lets you make an ok_button_action_performed method that just works. However, we don't raise an error anytime a method is created that looks funny, or writing your controller would become a pain. This means we get silent failure.

Perhaps we can abuse blocks in a future version where you can set up implicit handlers, and raise anything that doesn't match.

class MyController < Monkeybars::Controller
  define_handlers do
    def ok_button_action_performed
      ...
    end

    # oh noes! error raised!
    def typo_button_performed_action
      ...
    end
  end
end

Back to your problem though. Can you create vanilla handlers in your nested controller and see if you get output for them? Then we can look at making them fancy and working with define_handler. Make sure your button name matches what your handler thinks it is (:

Hi again,

I think it helps imagine what I was talking about, if I post some code:

class PopupController < ApplicationController
  set_model 'PopupModel'
  set_view 'PopupView'
  #set_close_action :exit
  #add_listener :type => :action, :components => [:ok_button]
  def ok_button_action_performed 
    p :ok_button_handler_called
    update_model view_model, :data
    p model.data
    close
  end
end


class PopupView < ApplicationView
  set_java_class 'popup.PopupDialog' 

  def create_main_view_component
    PopupDialog.new(nil, true)
  end

  map :model => :data, :view => "textfield.text"
end

Sven

I'll put some info on this thread as well (followd up on another dialog thread yesterday).

I'm trying something similar to this thread:

dialog view:

java_import "trade_filter_dialog.TradeFilterDialog"

class TradeFilterDialogView < ApplicationView
  set_java_class 'trade_filter_dialog.TradeFilterDialog'

  def create_main_view_component
    42
  end

  def parent_component=(parent)
    p "set parent component"
    @main_view_component = TradeFilterDialog.new(parent, true)
    @main_view_component.location_relative_to = parent
  end

end

dialog controller:

class TradeFilterDialogController < ApplicationController
  set_model 'TradeFilterDialogModel'
  set_view 'TradeFilterDialogView'
  #set_close_action :close

  def find_trades_button_action_performed
    p "find trades clicked"
    view_model.do_find = true
    update_model view_model, :do_find
    close
  end

end

in main controller: def tradetablekey_pressed(event) if event.keycode == KeyEvent::VKF3 @dialog = TradeFilterDialogController.create_instance addnestedcontroller(:dialog, @dialog) status = @dialog.open viewmodel.randomizetrades updatemodel viewmodel, :trades removenestedcontroller(:dialog, @dialog) update_view end

end

main view:

nest :sub_view => :dialog, :using => [:define_dialog_parent, nil]

def define_dialog_parent(view, component, model, transfer)
  view.parent_component = @main_view_component

end

if I run this and try to activate the dialog (via the F3 key press) I receive: Java::JavaLang::IllegalArgumentException - java.lang.IllegalArgumentException: Can not set javax.swing.JButton field tradefilterdialog.TradeFilterDialog.findtradesbutton to java.lang.Long java.lang.IllegalArgumentException: Can not set javax.swing.JButton field tradefilterdialog.TradeFilterDialog.findtradesbutton to java.lang.Long

If i comment out the setjavaclass in dialog view it runs and pops up the window, but the button of the window doesn't fire. My guess is that's because the button handler gets tied to the "first" component created by createmainviewcomponent (i.e. no bindings get made) and when I then switch @mainview_component it doesn't retie the actions to the new component.

It's a shame the google groups archive was removed, seems there's some threads there I'd like to read. I'd really like to figure out how to do a dialog but it's proving to be pretty hard going..