User forums > Nightly builds

The 07 June 2007 build is out.

<< < (4/5) > >>

Pecan:

--- Quote from: MortenMacFly on June 08, 2007, 08:48:21 am ---
--- Quote from: chikigai on June 08, 2007, 02:23:12 am ---Ctrl + PgUp/PgDn used to allow scrolling through the open files list.

--- End quote ---
Huh... that never worked for me, I checked the accelerators before. Is this something you setup yourself?


--- Quote from: chikigai on June 08, 2007, 02:23:12 am ---Now that it works to move to next/previous functions, has the previous feature been removed?

--- End quote ---
No, it shouldn't - I just need to find out where this is setup than it will return...

With regards, Morten

--- End quote ---

Ctrl-PgDn/PgUp is probably part of the wxNavigationKeyEvent used by popup_dlg.cpp in wxFlatNoteBook.

From wx2.8.4 source:

--- Code: ---// ----------------------------------------------------------------------------
// Keyboard handling - this is the place where the TAB traversal logic is
// implemented. As this code is common to all ports, this ensures consistent
// behaviour even if we don't specify how exactly the wxNavigationKeyEvent are
// generated and this is done in platform specific code which also ensures that
// we can follow the given platform standards.
// ----------------------------------------------------------------------------

void wxControlContainer::HandleOnNavigationKey( wxNavigationKeyEvent& event )
{
    wxWindow *parent = m_winParent->GetParent();

    // the event is propagated downwards if the event emitter was our parent
    bool goingDown = event.GetEventObject() == parent;

    const wxWindowList& children = m_winParent->GetChildren();

    // if we have exactly one notebook-like child window (actually it could be
    // any window that returns true from its HasMultiplePages()), then
    // [Shift-]Ctrl-Tab and Ctrl-PageUp/Down keys should iterate over its pages
    // even if the focus is outside of the control because this is how the
    // standard MSW properties dialogs behave and we do it under other platforms
    // as well because it seems like a good idea -- but we can always put this
    // block inside "#ifdef __WXMSW__" if it's not suitable there
    if ( event.IsWindowChange() && !goingDown )
    {
   

--- End code ---

cstudent:

--- Quote from: rjmyst3 on June 08, 2007, 12:12:09 pm ---
cstudent/killerbot:
Could the instructions for updating wxWidgest to 2.8.4 be put on the wiki and linked to in the nightly build announcement? This is becoming a common problem.

--- End quote ---

I hope to find some time this weekend to do just that. In the meantime you can check my post here.


EDIT: OK. Wiki is now updated to include how to install wxWidgets 2.8.4 on Ubuntu.

rjmyst3:

--- Quote from: cstudent on June 08, 2007, 03:06:25 pm ---
--- Quote from: rjmyst3 on June 08, 2007, 12:12:09 pm ---
cstudent/killerbot:
Could the instructions for updating wxWidgest to 2.8.4 be put on the wiki and linked to in the nightly build announcement? This is becoming a common problem.

--- End quote ---

I hope to find some time this weekend to do just that. In the meantime you can check my post here.


EDIT: OK. Wiki is now updated to include how to install wxWidgets 2.8.4 on Ubuntu.

--- End quote ---

thanks

bashinerox:
'kay, here goes..

Its not really too important, but its still, well, there..

When I declare i function prototype inside a class that is syntactically the same, but not an exact carbon copy (e.g. a missing space after a comma) of its definition, then call it from another function within the class, the parser for code completion sees it as a function overload:


--- Code: ---class testclass
{

    int func1(int x, int y);
    int func2(void);
};

testclass::func1(intx,int y)
{
 return x + y;
}

testclass::func2(void)
{
    func1(//at this point it comes up with two code completion selections. one with and one without the space.
}

--- End code ---

I dunno if it does it with anything other than removing a space (or if anything other than a space would be syntactically different -- its 1:40 am here, gimme a break..)

killerbot:
sames happens when you rename the arguments in declaration and definition, or in the declaration you don't name them.
CC lacks the parsing of the arguments at this moment, aswell as sometimes scope in inheritance" trees

Navigation

[0] Message Index

[#] Next page

[*] Previous page