User forums > Nightly builds

The 09 october 2006 build is out.

<< < (3/4) > >>

BCCISProf:
I am getting the following error while editing a file in this build:

Assertion[cpMaxL=pdoc->length()] failed at sdk/wxscintilla/src/scintilla/scr/editor.c xx5977


Did not get this error on previous builds. Using Win XP SP2.

Ceniza:

--- Quote from: mandrav ---Last time I used this in linux with wxGTK, I got more segfaults than I could handle :wink:
--- End quote ---

It'd be safe to remove from those flags then :wink:

So far the only set of flags I've found to cause problems with some gtk+-1.2.x configure scripts are LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s -Wl,--as-needed -Wl,-z,combreloc" (haven't tried to find the guilty flags in there, even though -s is not one of those), but they worked just fine when I compiled wxGTK.

My whole Linux installation (Gentoo) is compiled using -fomit-frame-pointer, among other flags, (including wxGTK and Code::Blocks) and it hasn't caused any problems yet :)

TheTuxKeeper:

--- Code: ---#!/ bin/sh
binaries=`find /usr/local/codeblocks -type f \( -perm +111 -or -name "*.ko" \)`
# Strip ELF binaries
for f in $binaries
do
        file_output=`file "$f"`
        case $file_output in
            *ELF*", not stripped")
                ;;
            *ELF*", stripped")
                echo "WARNING: "`echo $f | sed -e "s,^$RPM_BUILD_ROOT/*,/,"`" is already stripped!"
                continue
                ;;
            *)
                continue
                ;;
        esac
        strip [--strip-all | --strip-unneeded]  "$f"
done

--- End code ---
I took the /usr/lib/rpm/find-debuginfo.sh script of suse 10.0 (the one of 10.1 is different, don't know why) and removed unneeded things (object copying to .debug files and rpm specific things). I don't know whether --strip-all is a good idea or not, I think --strip-unneeded won't cause problems (I hope so :lol:).
Save this as a file, remove the space in the first line between "/" and "bash", replace [--strip-all | --strip-unneeded] with one of both options and run it as root with sh strip_codeblocks.sh. You can check whether te binaries have been stripped with for example file /usr/local/codeblocks/bin/codeblocks. A "stripped" should appear at the end ;)
I havn't checked whether the script really works, but theoretically it should  :lol:

lubos:
hello there
i noticed a bug in scrolling long(wide) files. it just stop scrolling at column 250 but there is 399 columns.when i use right mouse button it srolling normally.

i hope you understand :p
here is a small image:


can someone reply that?

thomas:

--- Quote from: lubos on October 10, 2006, 06:50:42 pm ---hello there
i noticed a bug in scrolling long(wide) files. it just stop scrolling at column 250 but there is 399 columns.when i use right mouse button it srolling normally.
--- End quote ---
Scintilla feature, SciTE behaves the same way... if you need to scroll past 255, you need to place the cursor, sorry.

On a different note: Although this is truly not good behaviour from the editor's side, you should ask yourself if there is the possibility that something is wrong with your code, if you have more than 255 characters per line.
It is certainly debatable and hard to tell what is "normal" and what is not, but I guess most people will deem 60-120 characters as normal widths. Maybe up to 150, but that's about the maximum.
Anything that is a lot wider is quite unreadable, even on huge screens (and being required to scroll horizontally is generally considered very unergonomic).

Navigation

[0] Message Index

[#] Next page

[*] Previous page