search for: bitmap1

Hi wxRuby Gurus, I''m trying to write a sample program which allows me to drag an image (by left_mouse_button down) across the canvas. I got it to work ... well, sort of. The problem is I can drag it only by clicking on the left top corner of the image and nowhere else. Besides, the dragging is not very smooth. How can I make it better? I am using wxRuby 0.6.0 on Win XP (Home) and

...bsp * \param const wxString& -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \param wxItemKind -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp*/ - - wxToolBarTool* AddTool(int toolId , const wxString& label , const wxBitmap& bitmap1 , const wxString& shortHelpString = wxT(""), wxItemKind kind = wxITEM_NORMAL) ; -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp/** -&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp&nbsp * \brief -&nbsp&nbsp&nbsp&nbsp&...

Add online resize in tunefs.ocfs2 so that user can increase the volume when it is mounted.

...olBar_addtool). ToolBar#add_tool </span><span class="cx"> </span><del>- "ToolBarToolBase":toolbartoolbase.html *add_tool*(%(arg-type)Integer% toolId, - %(arg-type)String% label, - %(arg-type)Bitmap% bitmap1, - %(arg-type)String% shortHelpString = "", - %(arg-type)ItemKind% kind = ITEM_NORMAL) </del><ins>+ Integer *add_tool*(%(arg-type)Integer% toolId, + %(arg-type)String% label, + %(a...

...pan class="lines">@@ -16,11 +16,14 @@ </span><span class="cx"> wxToolBarToolBase* AddTool(wxToolBarToolBase* tool ); </span><span class="cx"> wxToolBarToolBase* AddCheckTool(int toolId , const wxString& label , const wxBitmap& bitmap1 , const wxBitmap& bitmap2 , const wxString& shortHelpString = wxT(""), const wxString& longHelpString = wxT(""), wxObject* clientData = NULL) ; </span><span class="cx"> wxToolBarToolBase* AddRadioTool(int toolId , const wxString& lab...

...p nicely, so there's no reason why we can't use * the more specific cluster api to claim bits. */ @@ -852,6 +858,8 @@ static int ocfs2_local_alloc_new_window( goto bail; } + osb->la_last_gd = ac->ac_last_group; + la->la_bm_off = cpu_to_le32(cluster_off); alloc->id1.bitmap1.i_total = cpu_to_le32(cluster_count); /* just in case... In the future when we find space ourselves, diff --git a/fs/ocfs2/ocfs2.h b/fs/ocfs2/ocfs2.h index cd4a6f2..0462a7f 100644 --- a/fs/ocfs2/ocfs2.h +++ b/fs/ocfs2/ocfs2.h @@ -197,7 +197,6 @@ struct ocfs2_super struct ocfs2_node_map recovery...

...s loop state. */ #define EXECUTE_IF_SET_IN_BITMAP(BITMAP, MIN, BITNUM, ITER) \ for (bmp_iter_set_init (&(ITER), (BITMAP), (MIN), &(BITNUM)); \ bmp_iter_set (&(ITER), &(BITNUM)); \ bmp_iter_next (&(ITER), &(BITNUM))) /* Loop over all the bits set in BITMAP1 & BITMAP2, starting with MIN and setting BITNUM to the bit number. ITER is a bitmap iterator. BITNUM should be treated as a read-only variable as it contains loop state. */ #define EXECUTE_IF_AND_IN_BITMAP(BITMAP1, BITMAP2, MIN, BITNUM, ITER) \ for (bmp_iter_and_init (&(ITER),...

Hey guys, Wx::ToolBar#insert_tool, is either not referenced right, or needs to be updated. 1.) Wx::ToolBar#insert_tool(size_t pos, ToolBarToolBase tool) comes up with a No overloading function type error, AKA 404 Not Found 2.) Wx::ToolBar#insert_tool(size_t pos, Integer toolId, Bitmap bitmap1, Bitmap bitmap2 = NullBitmap, Boolean isToggle = false, Object clientData = nil, String shortHelpString = "", String longHelpString = "") Should have a reference also in the parameters to String label just after Integer toolId, to conform with Wx::ToolBar#add_tool(). Just thou...

...bail; + } + unlock = 1; + + } else { + status = ocfs2_read_inode_block(inode_alloc, &bh); + if (status < 0) { + mlog_errno(status); + goto bail; + } + } + + dinode_alloc = (struct ocfs2_dinode *)bh->b_data; + + fi->ifi_stat[slot].lfi_total = + le32_to_cpu(dinode_alloc->id1.bitmap1.i_total); + fi->ifi_stat[slot].lfi_free = + le32_to_cpu(dinode_alloc->id1.bitmap1.i_total) - + le32_to_cpu(dinode_alloc->id1.bitmap1.i_used); +bail: + if (unlock) + ocfs2_inode_unlock(inode_alloc, 0); + + mutex_unlock(&inode_alloc->i_mutex); + + iput(inode_alloc); + brelse(bh); +...

...its; status = ocfs2_journal_access_di(handle, INODE_CACHE(local_alloc_inode), @@ -811,7 +813,7 @@ int ocfs2_free_local_alloc_bits(struct ocfs2_super *osb, goto bail; } - while (num_bits--) + while (clear_bits--) ocfs2_clear_bit(start++, bitmap); le32_add_cpu(&alloc->id1.bitmap1.i_used, -num_bits); -- 1.8.4.3

...+ status = ocfs2_journal_access_di(handle, + INODE_CACHE(local_alloc_inode), + osb->local_alloc_bh, + OCFS2_JOURNAL_ACCESS_WRITE); + if (status < 0) { + mlog_errno(status); + goto bail; + } + + while (num_bits--) + ocfs2_clear_bit(start++, bitmap); + + le32_add_cpu(&alloc->id1.bitmap1.i_used, -num_bits); + ocfs2_journal_dirty(handle, osb->local_alloc_bh); + +bail: + return status; +} + static u32 ocfs2_local_alloc_count_bits(struct ocfs2_dinode *alloc) { u32 count; diff --git a/fs/ocfs2/localalloc.h b/fs/ocfs2/localalloc.h index 1be9b58..44a7d1f 100644 --- a/fs/ocfs2/loca...

...+ status = ocfs2_journal_access_di(handle, + INODE_CACHE(local_alloc_inode), + osb->local_alloc_bh, + OCFS2_JOURNAL_ACCESS_WRITE); + if (status < 0) { + mlog_errno(status); + goto bail; + } + + while (num_bits--) + ocfs2_clear_bit(start++, bitmap); + + le32_add_cpu(&alloc->id1.bitmap1.i_used, -num_bits); + ocfs2_journal_dirty(handle, osb->local_alloc_bh); + +bail: + return status; +} + static u32 ocfs2_local_alloc_count_bits(struct ocfs2_dinode *alloc) { u32 count; diff --git a/fs/ocfs2/localalloc.h b/fs/ocfs2/localalloc.h index 1be9b58..44a7d1f 100644 --- a/fs/ocfs2/loca...

...#// even though that''s not a documented class. -#// fake it by saying it''s just a control -typedef wxControl wxToolBarTool; </del><span class="cx"> </span><del>-%ignore wxToolBar::AddTool(int toolId, const wxString& label, const wxBitmap& bitmap1, const wxBitmap& bitmap2 = wxNullBitmap, wxItemKind kind = wxITEM_NORMAL, const wxString& shortHelpString = "", const wxString& longHelpString = "", wxObject* clientData = NULL); </del><ins>+// +%typemap(out) wxToolBarToolBase* { + int pos_of_tool = arg...

I'm running a bit late with the e-mail this time around, but I think that's ok since there really isn't any major new features here - the bulk of the Ocfs2 update is bug fixes, or cleanups. The same goes for configfs. The only two things that could be described as features would be: - Sunil has updated Ocfs2 to provide even more live cluster locking information via debugfs. - Joel