nav_bar_button class method

[jamonholmgren]

class MyScreen < PM::Screen
  title "My Screen"
  nav_bar_button :back, title: 'Back', style: :plain, action: :back

  def on_load
    puts "Nav bar enabled."
  end
end

[bitgangsta]

I like this a lot. The only thing that has been scratching my head sometimes is the load order of things under RubyMotion. I know you can configure dependancies in App, but I still find issues sometimes (particularly with things like fonts being registered etc). By making this a class method, are we going to hit any similar limitations?

Diving into the Teacup source, they solve this issue elegantly by storing styles until they are needed / queried. So perhaps I suggest evaluating the actual call during on_init rather than when the class itself is instantiated. What do you think?

I know it would help me as I'm trying to use a custom font. Perhaps others will hit similar roadblocks.

Daniel

[bitgangsta]

(i.e. the class-level nav_bar_button just stores its args, but doesn't actually call set_nav_bar_button until on_create or something)

[jamonholmgren]

That's my thought as well, except I plan to add it in the add_nav_bar call:

https://github.com/clearsightstudio/ProMotion/blob/edge/lib/ProMotion/screen/screen_module.rb#L48

[ryanlntn]

@jamonholmgren I'm closing this since it looks like this was resolved back in February with the 2.3 release.