Contribute/Bugsquad/BugDays/KOfficeDay2

< Contribute‎ | Bugsquad‎ | BugDays
Revision as of 23:29, 23 January 2009 by Dtritscher (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Introduction

KOffice Bug Day 2 will take place on Sunday, January 25th 2008. We will coordinate the day from #kde-bugs on irc.freenode.net, so if you are not already in that channel, please join it.

The aim of the Krush part of that day is to discover as many bugs as possible in various KOffice applications so they can be fixed before the final release of KOffice 2.

Requirements

You don't need any programming experience to help out with Krush Days, but you will need a recent version of KOffice, either svn trunk or the recent KOffice 2.0 Beta 5.

Installing from SVN

Information on setting up KOffice from trunk can be found here. If you're having trouble installing KOffice, feel free to drop by on #kde-bugs early to get some help. You don't need KDE 4.2 to compile KOffice. The 4.1 development packages are sufficient.

Installing using your distribution's packages

If you're lucky, your distribution already provides packages of KOffice 2.0 Beta 5:

  • Debian: available in the experimental repository (more information)
  • openSUSE: available for 10.3, 11.0 and Factory, using the Build Service within the KDE:KDE4:Factory:Extra-Apps repository (more information)
  • Mac OSX: KOffice Beta 5 is available on macports (more information)
  • Kubuntu: Available in the kubuntu-experimental PPA (Follow KDE 4.2RC1 instructions on Kubuntu.org)

Applications put to test

We'll test all applications release with Beta 5:

Apart from that KOffice contains reusable components called Flakes. Those components (plugins) provide additional content objects you can reuse in any of the KOffice applications. We'll be trying:

  • Charting Shape - formerly known as KChart

Preparations

Select an application you would like to test. Then, go to that application's section below on this page. Carefully read the application-specific hints as some applications have known bugs in Beta 5 and are likely to work better if compiled from trunk. If you match the requirements, add your name and svn revision number to the list of testers for that app.

Workflow

  1. Testdrive the application. The testing procedure is pretty much up to you but following some use pattern might be a good idea for a start (eg. try to create a real presentation) as that would probably exhibit the most annoying bugs (those most people are hit by). After you're done with that, try doing more obscure things and checking out as many of the buttons and options you can. Using features you're not using normally can provide some fun and help you finding bugs as well. (Of course you can also click around and smash your keyboard erratically to see what happens)
  2. Try to be thorough. If there's more than a way to accomplish a task, try all of them. If you've already been using an application in the past and remember a bug you encountered, try if it's still there.
  3. You encounter a bug.
    1. Check if someone has already put that bug in the appropriate section. If so, put that you can reproduce the bug below adding more details if you found any.
    2. Enter new bugs in the appropriate section giving as many details as possible. Remember, the more information there is the easier it will be for the developers to fix the bug.
    3. If the application crashed for you, try to get a good backtrace, paste it on pastebin or any other paste website (please make sure your paste doesn't expire in less than 6 months). Put the link below the bug. We'll pick it up later when the bugs are being filed. Due to the nature of KOffice, please try reproducing a crash you encounter in the other KOffice applications by using the crashing program's flake shape (if you're unsure about how to do that, please ask on #kde-bugs).
  4. If you're unsure about a bug, you can ask others on IRC if they can reproduce it as well.
noframe
 
Warning
Do NOT use rafb.net/paste as it expires after 24 hours. Use pastebin.ca instead.


Wrapping it up

After a while we'll start filing the bugs on bugs.kde.org. It's best to file bugs others have already confirmed because like that the developers will only get the good stuff.

Hints

  • You can edit single sections of this page if you you check Enable section editing via edit links in your TechBase Preferences.
  • Sometimes you might encounter edit conflicts if several people are working on the wiki page at once. We can mostly avoid those by keeping notes of the bugs we encounter in a text editor and file several of them later at once (don't forget to save).
Ktip.png
 
Tip
Please be sure to sign every bug or comment you add to this page with your irc nickname. You can use the wiki markup ~~~ to insert your wiki username automatically (but only do this if it is the same as your IRC nickname, otherwise write your IRC nickname in by hand).


Applications

Some application specific tips are given in the sections below.

General KOffice

Application specific tips

This section is meant for bugs concerning all of KOffice (eg. general problems with flake shapes or the user interface).

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma svn trunk r916627 starting
jtamate svn trunk r913209 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

noframe
 
Warning
The general bugs section is done. Please don't change anything in here. Open bugs should be followed on Bugzilla from now on.


Still valid (and reported)
  • In Frame/FrameSet Properties. Every time the "Retain Original Aspect ratio", the frame is made bigger.Jtamate
    • Hint: Not every frameset options dialog has it. If selected it continuously ZOOMS. Lemma
  • The menu "Configure Frame/Frameset>" is allways empty (until now). Jtamate
  • In the table flake, the first line can be edited only with the keyboard (tabs), but next lines, once the enter key is pressed, the editing text is displayed at the right (or bellow right), until it gets out of the table. Tested in kpresenter. Jtamate
    • Works even less currently. Keyboard navigation basically works but isn't reflected in the UI. Lemma
  • Print Preview does not show any text (in kword, will test later in other apps). Jtamate
    • I tried in KWord and KSpread with no luck (bug #185973). In KSpread Print Preview currently doesn't even open the preview window bug #185974 Lemma
  • I think it's not really intuitive that the checkboxes right next to categories/scripts in the Script Manager disable said scripts in the menu. Lemma Thought about it again and now I don't feel like this is bug-worthy. Lemma
  • If you disable a script in the Script Manager it shouldn't show in the Scripts menu (after all it seems the only reason to disable a script is to not accidentally click it). Lemma bug #185976
No longer there
  • The zoom options toolbar is not painted totally. Look at:

Zoom options.png
Jtamate
No longer valid. Zoom doesn't seem to have a toolbar of its own any longer and is now in the status bar. Lemma

  • The zoom options toolbar does not select the default tool (zoom in or zoom out). Jtamate No longer valid. Zoom doesn't seem to have a toolbar of its own any longer and is now in the status bar. Lemma
  • If you resize a docker to its minimum size, its resize handle vanishes therefor making it impossible to make it bigger again (can reproduce for dockers docked left, right or top but not on the bottom). Lemma No longer reproducible. Lemma

KWord

Application specific tips

At Beta5 the state of KWord is that the application has been stabilized to a large extend and all present features should work with small exceptions. The loading and saving of documents has not received a lot of attention and therefor it is well known that there will be loads of problems in loading ODFs. So testing KWord by loading may give you some silly results beware of that. And I'd rather have interaction and new document creation be the focus of testing due to that. (ThomasZ)

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Grundleborg r916455 In progress...
Blauzahl r916720 Let's go!
m4v r917484 I'm done.

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

Dunno
  • After starting kword, with the colorful document, the default tool is Text Editing, without doing anything else, when I choose Paragraph tool, the options bars docker suffer a little colapse. Look at:
    Kword toolbar1.png
    Jtamate
    • NOTE: It happens also with a lot of tools.
    • NOTE: This only happens with the colorful document, with a blank document it does not happen.
    • I get an overlay like this in krita: The "snapping" box over the upper left hand area of the main thing. So maybe it is something common?Blauzahl
      • Apparently the technical term is "docker". "small gray block with fancy items that's never in the place you want it"--slangkamp
  • The tool toolbar can not be horizontally srinked to only one or two tools (specially usefull on small screens). Jtamate
    • NOTE: This only happens with one user account (that has used previous betas), with a fresh new account it does not happen.
    • Can't reproduce with my user either (and I did use previous version with it). Can this be considered fixed? Lemma
    • Acc. to Jtamate reproducible using this config: [1]
  • With a chart in a document, autosave crashed (unfortunately I can not provide backtraces) Jtamate
    • I didn't get that. However I don't know if autosave kicked in somewhen. Lemma
  • Predefined Format does not revert paragraph formats. Jtamate
    • I'm not quite sure I know what you mean. Default format? I think I don't know which menu item I need to test this. Lemma
  • The paragraph formats does have some problems with the second line in the right part. It is always displaced to the right. Jtamate
    • Not sure I understand what you mean. Lemma
  • Selecting "character tipography", in spanish "tipo de letra", there is no tipography preview (very usefull). Jtamate
    • Couldn't find this option. Lemma
  • Selecting "character tipography", in spanish "tipo de letra", the cursor is a hand in the tipography, but not in the size or format. Jtamate
    • Couldn't find this option. Lemma
  • Default initial font is insanely small. Smaller than the icon fonts. Barely readable here. Blauzahl
    • For me the default font size is 12pt. Can you still reproduce? Lemma
  • I save a document as a .kwd. I then try to open a new copy of it, and get this message: Could not open blah.kwd Reason: Parsing error in root at line 1, column 1 Error message: unexpected end of file Blauzahl
    • I can't save to .kwd. Lemma
  • if you use the default tool for 'select' the page, then edit -> delete page does not crash, but undoing doesn't return the text, just an empty page. m4v delete page seems disabled. m4v
    • Somehow I got strange crashes as well for this one. But still not sure what I did to make it happen. Lemma
  • the indenting handles in the ruler only work in the single line where the cursor is, selecting a paragraph doesn't change this. I would expect them to affect the whole document unless there's selected text. m4v
    • Seems intuitive for me. But maybe the behaviour changed and we're seeing different things. Lemma
Still there (and reported)
  • Changing to some tools, the window height is increased beyond the screen limit. Jtamate
  • When the view is divided, the toolbars dockers are multiplied. Look at:
    Duplicacion.png
    Jtamate
  • In decoration (text properties), the ... button clears the color section. Is not better a <x button? Jtamate
    • Has an icon of its own now (broom with an X) Lemma
  • if you add a shape in a paragraph, the text moves around the shape, but if you next delete the shape, the text doesn't returns like it was before. m4v
  • creating a shape with a stroke width really big, like 20, can hide the text around it. m4v
  • undoing can fail. m4v
    1. write several lines of text, I tried with 6 lines with a word each
    2. select all the lines, and hit backspace
    3. ctrl+z for undo, not all lines are restored
  • crash while using split view. m4v
    1. start a blank doc.
    2. split view
    3. try *right* clicking in one view or the other, eventually I get a crash.
No longer there
  • Find does nothing. Hope the find interface will change to something similar to what kate has. Jtamate Find works for me. Lemma
  • The hand drawing plots are not saved (or loaded). What I wrote:

Screen with free hand drawings.png
But only the text is restored. If there are some things that can not be saved or restored, it should be shown when saving the file.Jtamate
Paths, handdrawn paths and calligraphy paths save and load again correctly for me. Lemma

  • There is no menu entry to configure Kword (including Autosave time) Jtamate
    • This had been reported as bug #181604. It was closed as the issue is known and the developers don't plan to include this in the 2.0 release. Lemma
  • Overstriking more than one text line, only does it good in the first line. The others get overstriked at the end. Jtamate Works as expected now. Lemma
  • Open document dialog is giving me a one line list of files, ie one row, no columns. Very hard to read. Probably in other areas of koffice. Blauzahl
    • I now get the default KDE file open dialog. Lemma
  • crash when deleting a page m4v delete page seems disabled. m4v
    1. start a blank document
    2. write something
    3. add a page break
    4. write something more
    5. edit -> delete page
    6. crash
  • crash when selecting any template from the envelopes or cards and labels groups. m4v fixed m4v

KSpread

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma svn trunk r876329 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

noframe
 
Warning
The KSpread section is done. Please don't change anything in here. Open bugs should be followed on Bugzilla from now on.


KPresenter

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
dtritscher beta5 Kubuntu starting
JLP SVN trunk r916636 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

noframe
 
Warning
The KPresenter section is done. Please don't change anything in here. Open bugs should be followed on Bugzilla from now on.


  • KPresenter crashes when selecting the "animation tool" from the default toolbar. See [2] for backtrace. dtritscher FIXED in trunk shortly after the beta was packed Zagge
    • It doesn't crash for me. Three dockers show: Click actions, Transitions, Shape animation. JLP
  • Kpresenter crashes with the kspread shape. I was doing a lot of things. I do not remember exactly what. See http://pastebin.com/m2cbc89f2 Jtamate
    • For me table shape crashed when trying to select a sheet from the dropdown list. Here is the backtrace I get after adding another sheet and then trying to select it: http://pastebin.ca/1317888 You don't need to add any new sheet, trying to select existing selected one is enough for crash. JLP
    • As a matter of fact this happens for all KOffice applications. Lemma bug #186626
  • Setting a large picture for background doesn't make the picture fit the slide size. Only part of the picture is shown. JLP Fixed in commit 917188 Zagge
  • Double clicking on a placeholder for picture shows file selector dialog twice. JLP FIXED in commit 916817 Zagge

KPlato

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Lemma r916627 starting
Blauzahl r916627 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

noframe
 
Warning
The KPlato section is done. Please don't change anything in here. Open bugs should be followed on Bugzilla from now on.


Done

  • Crash when expanding a resource group in "Resource Assignments". Reproduce:
    1. Add a resource group
    2. Add a resource
    3. Add a schedule and calculate it
    4. Selecte "Resource Assignments" and expand try to expand the resource group
    5. Backtrace Lemma
  • Fixed r926777. Dag
  • Clicking most of the things in the Styles docker seems to crash KPlato, eg.
    • Clicking the clear style (X) button: Backtrace bug #186631
    • Selecting gradient and clicking the gradient chooser: Backtrace bug #186633
    • Crashes on choosing texture as well. Not always 100% reproducible, but if I click around a little I always manage to crash it. Lemma</s> Equal backtrace to the previous one. Lemma

Fixed in r879929. Dag

  • No hint as to how to modify certain items' names as there's no context menu (or just no menu item). Pressing F2 or double clicking is not obvious to everyone. bug #186630
    • Calendar name
    • Account name
    • Resource Group
    • Schedule Lemma
  • Inserting dependencies using in list mode is counter-intuitive (at least to me): If I select a task and one of the available tasks I guessed that pressing the green arrow would add a dependency. However I intuitively assumed that I'd get a finish-start dependency from column 1 to column 2, not vice-versa. Lemma Thought about it again and think it's not worth filing a wish as it is kind of clear if you read carefully :). Lemma
  • WISH: It would be nice if the graphic dependencies editor would already perform basic scheduling, example:
    1. Add tasks T1, T2, T3
    2. Add 2 subtasks ST2.1, ST2.2 below T2
    3. Insert a finish-start dependency from ST2.1 to ST2.2
    4. Insert finish-start dependencies from T1 to T2 and from T2 to T3
    5. The dependency viewer doesn't give a graphical indication that T2 "contains" ST2.1 and ST2.2. Even after performing a schedule the view stays the same. I would have assumed for it to show data similar to the gantt view. Lemma bug #186634
  • WISH: Check which settings are per-project and which are application-wide. Most of the current items in Settings->Configure KPlato would also make sense in the Project Settings dialog. (As a matter of fact the Settings dialog seems to be per-project which was not obvious.) Lemma bug #186635
  • Crash trying to export a project (empty) to PDF: Backtrace Lemma

Fixed r183940 Dag

  • Crash trying to view print preview (backtrace from empty project): Backtrace Lemma

Fixed r183940 Dag

  • Strange graphic glitch:
    1. Select a view/editor from the view selector
    2. Collapse its category
    3. Expand the category again
    4. Result: The list item is still selected but its background is yellow instead of the default background (Oxygen blue for me). Lemma bug #186636
  • WISH: Add more (and more obvious) keyboard control for entering and modifying tasks and resources. Examples:
    1. Add task or resource using keyboard
    2. Modify task using keyboard (Enter in the lists may open the edit window)
    3. Allow to modify stuff in place in a more spreadsheet-like manner (eg. duration estimate for tasks by just typing the numbers) Lemma Found out this mostly works already. Lemma
  • Wrong cursor when wiring dependencies graphically. Hovering the start- or endpoint of a node shows an up-arrow to indicate I can start wiring up there. Lemma bug #186639
  • I don't understand what the green rectangle is for inside the tasks in graphical dependency editor mode. Lemma
  • Unable to save file when document encryption is selected in File->Document Information and wrong error message: "Could not save <filename>. Reason: Could not create the file for saving" Lemma

Fixed in kplato r926998. Patch to koffice libs pending. Dag

  • File->Document Information->Author->Title is not saved. Lemma

This is in koffice libs. Fixed r926798. Dag

  • A document saved as "Uncompressed XML Files" can be saved but not opened. Lemma bug #186734
  • Not obvious that Saving as "KPlato project management document (Uncompressed XML Files)" will create a directory and store the actual files inside. Lemma bug #186736
  • File->Import/Open seem to do the same thing. I expect Import to either load the specified document's contents into the current document or handle file formats with a lower level of support than Open. Looking close it seems Import uses the existing file as a "template". Lemma bug #186737
  • Still in "cost breakdown structure". Hitting "add subaccount" a bunch of times to see how recursive I can be... After the 4th, I get drawing problems. See screenshot: picture Blauzahl bug #186740

Dunno

  • Still in "cost breakdown structure". Now trying to edit my many subaccounts. It seems like "description" has vanished for the ones I can't "see". Blauzahl
  • WISH: A wizard would be nice, I have no clue how to start with anything on this app. Blauzahl I'm told it is close to other apps otu there.
  • Cost breakdown structure -> Add account: I expect to be able to tab into the Description field, instead I have to double click. Blauzahl
    • asking usability: navigation is currently arrow keys and F2 to edit n] Maybe it's just a matter of adding in tab? If possible? Blauzahl

Karbon

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
m4v svn r916284 i'm done.
Enkithan svn r916340 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

noframe
 
Warning
The Karbon section is done. Please don't change anything in here. Open bugs should be followed on Bugzilla from now on.


Still there and reported

  • Using Tie shapes is unintuitive at first, since they don't connect shapes when you create them, you need to connect them after the Tie is created. m4v bug #186934
  • Crash when you select text and delete it with the backspace in a Text shape, apparently this is a qt bug, fixed in 4.4.4? bug #175911 m4v
    • this one is related to the kotext library, so not specific to Karbon bug #186935
  • The first time the pop-up color selector is used, the widget isn't updated Enkithan
    • unfortunately i cannot reproduce that jaham
    • I can't reproduce that exact bug but changing style while the calligraphy tool is active doesn't changes the last selection's style instead of the current shape's one. Lemma bug #186937

Already fixed

  • Tie shapes are invisible when created, since their stroke width is zero. m4v - this should be fixed in trunk, need to confirm. FIXED m4v
  • Tie shapes aren't preserved when you save as odg. m4v FIXED m4v
  • Shapes are invisible in outline mode Enkithan FIXED jaham
  • Crash: create an artistic text shape, delete all the text (leave it empty) and enter. if you try to resize the shape it crashes. m4v
    • the shape behaves better now when all text is deleted; when the tool is deactivated with an empty shape active, that shape will be deleted (probably needs some testing if that is acceptable behaviour) jaham
  • aligning grouped shapes doesn't work as expected, they move to the margins of the page. m4v FIXED m4v
  • The size of the Artistic text shape can't be updated from the geometry docker, same for grouped shapes. m4v FIXED jaham
  • if you double click in a group that has an artistic shape inside, you get to edit the text, but the blinking cursor isn't placed were you would expect (i see it near the top page margin). m4v FIXED jaham
  • when you do a path operation with a skewed shape, the resulting shape has another transformation (is easy to see if you apply a gradient to the shapes). m4v FIXED jaham
  • Paint a long, very very "spiky" line with the freehand path drawing tool (with precision set to curve): karbon freeze but doesn't crash. Enkithan
    • No real freeze here, it just gets really really slow if the line is really long. Lemma

Krita

Application specific tips

Application specific tips go here.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
Brot svn trunk r914546 starting
dtritscher beta5 starting
Enkithan svn trunk r916340 starting
m4v svn trunk r916627 I'm done.
Blauzahl r916720 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

Still there and filed

  • Filter paintops all have a black or empty output (except Invert that works as expected). Enkithan bug #186948
  • Values of input boxes of the Filter paintop dialogs cannot be changed (it switches back to the default value as soon the value is entered). Enkithan bug #186950
  • In the Stroke Properties docker, you can't edit the path's width by writing it with the keyboard, only by clicking in the arrows of the textbox. m4v
  • When you change the path's width trough the stroke properties docker, the width is reset again when you paint a new path. m4v
  • if you select a tool for create a selection and then the freehand tool the freehand tool no longer draws. m4v
    • if you create a selection, and then use the freehand tool, instead of drawing it will create a selection. m4v
    • filled as bug #185637 m4v
  • switching from the mouse to the stylus doesn't activates the stylus's previous tool. m4v
  • merging between flake layers should result in a flake layer. m4v
  • bug that deletes what you did on your flake layer. m4v
    1. draw something with the freehand tool (or anything that creates a flake layer)
    2. create a new paint layer, it should be added over the flake layer
    3. move the new layer below the flake layer, (use the down arrow of the docker, dragging the layer with the mouse doesn't trigger the bug)
    4. what you did in the flake layer disappears
  • duplicated layers doesn't update when you do undo. m4v
    1. start a new white document
    2. duplicate the layer
    3. paint something
    4. undo
    5. nothing is updated
  • after you finished drawing a path, tools like the brush paint are disabled, you need to switch layers to enable them again. m4v
    • same for freehand and calligraphy tools. m4v
    • related to bug #185767 ?
  • using the 'select a continuous area of colors' tool, with fuzzines set to zero, does not selects anything, set it seems to select something, because you can't paint anything until you hit "deselect" in the menu. m4v
  • the sumi-e brush can be very cpu intensive, it only takes to set the radius to 50 (which isn't that huge) to make krita freeze on my computer. m4v
  • using the transform tool in a selection still applies the transformation in the whole layer. m4v
  • managing the layer stack with the stylus is really hard. m4v

Dunno

  • [usability for mobile devices] If you start in a smaller screen, there is no word wrapping/etc for the RGB options, so it looks like there are four options of "Transpar...", all of which are the same. Clicking to see what they are is annoying. Blauzahl
    • Where are those RGB options? Lemma

Aren't reported yet

  • the fuzzines option in the 'select a continuous area of colors' and 'select similar colors' tools does not work as expected if the layer was initially transparent. m4v
    • screenshot: media:Krita_krush8.jpg the select tool discriminates between two colors, but not between a color with different opacity in a transparent layer, note fuzzines set to 1.
  • sometimes the freehand fails to create a path. m4v
  • the color of the visual aid of tools like draw straight lines, rectangles, etc is always black, it makes difficult its use in dark backgrounds. m4v
  • you can't finish drawing a path with shift+click, this is inconsistent with other tools like polyline, you need to double click to finish the path, note that double clicking with a tablet stylus is truly hard. m4v
  • sometimes the freehand fails to create a path. m4v
    • screenshot (precision set to curve)
    • (fill as a Karbon bug since the freehand is a karbon tool)

Already fixed

  • Selecting some tools, the tools options are drawn over the picture, not in the default place. Jtamate
    • I can no longer reproduce after updating and removing my kofficerc and kritarc files. Lemma
  • Selections with polygon and lasso tools are not visible when being drawn, making it nearly impossible to use. Enkithan That's because the temporary selection is white. It is visible on any other background color than white. Enkithan
  • Zoom with the slider doesn't quite work, if you set 100% you get a really really small image, when it isn't. m4v
    • It turns out the zoom slider has two modes, there's an icon at the right of the slider for that. Selecting it fixes the problem, I'm not sure what's the use of the other mode though. m4v
  • selecting the path tool adds the snap docker at the top left corner, over the toolbar and menus. m4v
    • No longer reproducible for me after updating and removing kritarc and kofficerc. Lemma
  • the path tool seems to have a width set to 100px always. m4v
    • slangkamp pointed out this is a bug with the templates, using a custom one doesn't show this behavior. m4v FIXED in trunk Slangkamp
  • The 'hide selection' option in the select menu has no effect. m4v FIXED Slangkamp
  • playing a recorded macro seems to cause a crash no matter what I try to record. m4v
    • disabled in trunk m4v
  • if you subject the toolbar to a clicking spree, you can make it look like there are several tools active. I can only achieve this with the tablet stylus though. m4v

Charting Shape (fka. KChart)

Application specific tips

You can add a chart in any of the KOffice applications as it's one of the flake shapes. Just select it from the "Add Shape" toolbox and drag it into the document area.

Testers

Please put your IRC nickname and KOffice svn revision number (or beta5) in the table if you are testing this app.

IRC Nickname KOffice svn revision number tested Testing details
JLP SVN trunk r916636 starting

Bugs

Please list all bugs found in the application below here. Remember to sign every comment you write on this wiki page with ~~~.

  • By default, the kchart should be gruped. It is quite difficult to put it at good shape again. Tested in kpresenter. Jtamate
  • Some other options on Legend tabdon't work, for example Show Frame, and Position and Alignment. JLP

This page was last modified on 23 January 2009, at 23:29. This page has been accessed 5,948 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal