search for: my_handl

Hi all, When using sortable lists, a click anywhere in a <li> element will trigger the "sort_by_dragging" mode, and have the clicked element follow the mouse. The active area is the entire <li> element. Is there a way to either : - limit the active/triggering "area" to a part of the <li> element (like a luggage handle) or - prevent a part of the

hi people I don''t know much about ajax - jquery. And right now I need to use some functionality with them. In a form (sales model) I have the following code: <div> <%= f.label :product_id, "Product" %> <%= f.collection_select( :product_id, Product.all, :id, :name, options={} ) %> </div> <div> <%= f.label :price,

...s patch adds the ability to call the sortable_element helper without the :url parameter. This can be useful if you want to handle the order update yourself and avoid calls to a remote action each time the sort order changes. Example: <%= sortable_element("my_list", :handle => "my_handle" ) %> If you try to do something like this in the edge version it won''t work but used to in 1.2.X. Looking for advice or +1 :-) http://dev.rubyonrails.org/ticket/10813 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to...

> We should also think about how to call std::terminate when cleanup dtors throw. The current representation for Itanium is inefficient. As a strawman, I propose making @__clang_call_terminate an intrinsic: … That sounds like a good starting point. > Chandler expressed strong concerns about this design, however, as @llvm.eh.get_capture_block adds an ordering constraint on CodeGen. Once

...> Chandler seems to be OK with get/set capture block, as long as the codegen > ordering dependence can be removed. I think we can remove it by delaying > the resolution of the frame offset to assembly time using an MCSymbolRef. > It would look a lot like this kind of assembly: > > my_handler: > push %rbp > mov %rsp, %rbp > lea Lframe_offset0(%rdx), %rax ; This is now the parent capture block > ... > retq > > parent_fn: > push %rbp > mov %rsp, %rbp > push %rbx > push %rdi > subq $NN, %rsp > Lframe_offset0 = X + 2 * 8 ; Two CSR...

This patch isn't complete (patch 6/6 isn't finished) so it's just for discussion, although it does compile and run. This introduces to nbdkit a concept of "filters" which can be placed in front of plugins to modify their behaviour. Some examples where you might use filters: * Serve a subset of the data, such as (offset, range) or a single partition from a disk image.