[krita] [Bug 424643] Can add to krita new export command on terminal for all Layer export? like export layer py plugin.
https://bugs.kde.org/show_bug.cgi?id=424643 --- Comment #5 from ferweer --- (In reply to Boudewijn Rempt from comment #3) > C++ and Qt. Commandline options are defined in KisApplicationArguments.cpp > and used from KisApplication.cpp Thanks, I checked this file. Yes sorry for im not programmer. Maybe i might saw only. (In reply to Boudewijn Rempt from comment #4) Woah. That is kindness community. Okay thanks, I try. But you said shouldn't be that difficult. I hope that is so. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423960] kdenlive if missing file path, can search but didn't replace missing file path.
https://bugs.kde.org/show_bug.cgi?id=423960 ferweer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from ferweer --- (In reply to emohr from comment #1) > This problem should be fixed a couple of days ago. Please try with the > master > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/. > > Be aware that the master contains a new project file which is not backward > compatible. Sorry late, OK I confirmed. Thanks fix! So I did change this issue status for resolve. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] Krita on master (after RR) cannot save and/or open layers with layer styles
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #9 from ferweer --- (In reply to Tymond from comment #8) > Note: situation on master with resource rewrite right now: > - Krita can open file with layer styles, it just won't be loaded. > - Krita can save file with layer styles, the layer style just won't be saved. Hi thanks. Krita Version: 4.3.0, Qt version compiled: 5.12.8 This version can save and load layer styles. So I using. But you right. I must not using of my work with krita development build. Sorry. So I changed krita version to distory default version. I think, And other developer said is linux application is all must using to new version of include development version as one can. But that is different. I understanded. thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #11 from ferweer --- I can close to this case? I don't know is change status is okay ? reported> resolve. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #10 from ferweer --- (In reply to Tymond from comment #9) Hi, Really kindness tips. thanks! 1,use filter layer that good comparison to colorize mask default. Deplorable point> No global. If you did update on colorize, This is have glitch color with auto change background. But this method is good kindness for eye at present. very thanks. If i use colorize, I use this method. 2. Change canvas background color. Sorry I don't like to dazzling background color. And i think. I want changed is my monitor to new. But what monitor is good and kindness for eye. I don't know. Yes i in the Darkest room. And maybe you think to eye pain case with sick? I no use spectacles. But i continuously to have kindness for my eyes future. thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #8 from ferweer --- (In reply to wolthera from comment #4) > Just so we're not confused, are you actually experiencing pain, or is this a > hyperbole in an attempt to get us to change this? > > The make/model of your screen can at maximum show 250 cd/m², and sRGB is > generally supossed to be at 80-100. I asked for it because it might be that > you would have an HDR monitor (you don't, these are at 1000 cd/m²), but > these devices do not work properly on Linux yet (graphics drivers don't > support them). This would have changed the nature of the bug significantly. > > > We cannot make this 'transparent'. My best guess is that we either switch to > use the canvas color or a different theme color. Hi, thanks kindness. And i get pain to eye. I means not hyperbole. I just think krita is good painting software. So I think and means is krita is can have better kindness with settings change? So because i one suggested. Just not compulsion. If this case is no change? I no anger, And no sad. And thanks you tried it. Hm, I suggest is cream > gray, or dark gray. But that is difficult? okay, Thanks for you tried and challenge. Krita colorize is needed for brightness gap and contrast gap. I understanded. I must try other method. Not using colorize mask. Eyes is very important. of course other body too. =) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #7 from ferweer --- Created attachment 130405 --> https://bugs.kde.org/attachment.cgi?id=130405=edit screenshot 1,2,3, colorize mask have gap -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #6 from ferweer --- (In reply to vanyossi from comment #3) > I don't understand. If pure white is causing eye strain its possibly a > brightness monitor setting. The tool starts using a semi-opaque white so it > takes some of the color of the layers below. In my ccase I use dark cream > color as a base for my sketches and using colorize mask has no harsh effect > over my eyes as the transform visual cue converts into a soft cream color. > > In anycase we need a visual cue to show the tool is active and ready to be > edited. If white can be problematic I wonder what can be done as an > alternative Hm. Yes i know that it. Because i just set dark brightness and kindly contrast settings on monitor. And i checked, Surely, Mask color is base background + #FF color = cream brightness color. I add screenshots. background color is always i using brightness color. that not brightness. Yes small setting window view = kind for eye. So, screenshot2 But anyways view not small. Screenshot3 means canvas background color to dark of krita settings. you can see scrennshot3? I think that is krita colorize mask is have gap contrast. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424643] Can add to krita new export command on terminal for all Layer export? like export layer py plugin.
https://bugs.kde.org/show_bug.cgi?id=424643 --- Comment #2 from ferweer --- (In reply to Boudewijn Rempt from comment #1) > Yes, something like that can be coded of course. But it will need a > volunteer to work on it. Hi, thanks. If i know that programing knowledge, I can did that it. Yes of cause that is a maybe. im not programmer. But i think, If i any do try, Maybe it is good of the get knowledge. krita sources> what filename to command line script code file? So C++ or QT? I remember, maybe krita said to using QT and C++. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424643] New: Can add to krita new export command on terminal for all Layer export? like export layer py plugin.
https://bugs.kde.org/show_bug.cgi?id=424643 Bug ID: 424643 Summary: Can add to krita new export command on terminal for all Layer export? like export layer py plugin. Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY hi,sorry for strange english. so this about request. Can add Krita new terminal command for export all layer? Option1 > No trimming transparent or background space. This option is did not trimming transparent. So no trimming background and layer, What that? Example, all image without change on canvas position. So kind for bone animation system. Or picture story animation. > Kind for this method using other software. example. Synfig studio, COAtools in blender. Option2 > Trimming transparent or background space. This option using trimming for transparent, or background no draw space. i think not difference transparent = background no draw space. But You can imaging example easy word. So, this like Gdquest https://github.com/GDquest/krita-batch-exporter. This plugin all trimming for transparent on layer. Image position on layer = Image center always. Why this request? Here. I can tell why i need this. I use krita in linux command on terminal. that is do export. that is wonderfull. I no need many confirm. that is very slow action. So >Export where directory? >E xport png? or jpeg? or other extension? >Export ok? this means confirm for overwrite. >Export name is what name? >Export done you must did more push button action. here. OK ugh, sorry. Yes, this terminal command method is very usefull. Thanks for package this command system on krita. By the way, This method always include all layer only. So I want difference option on krita terminal command. So i told that. Export separate all layer on terminal command. Optional command for No trimming, Or do trimming. Yes krita have Export Layer python plugins. But need more action GUI. >What You need document? You must do click select. >Where you need export >directory? You must choose directory path. this script close window, that >reset. If you need one more, This need action again. >What you need export extension is JPEG or PNG? Default JPEG, You need PNG? oh >one more click JPEG>PNG. This all action. Need moremoremoremore click. boring. And slow. Yes this method kind for user of no using terminal. And Gdquest. This plugins did trimming only. I want not trimming. So those plugins, Need krita GUI always. I want export only on cui of terminal. Krita Version: 4.3.1-alpha (git f119f41) Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-42-lowlatency Pretty Productname: Ubuntu 20.04 LTS Product Type: ubuntu Product Version: 20.04 Desktop: KDE -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424570] scroll bar issue on work space save window.
https://bugs.kde.org/show_bug.cgi?id=424570 --- Comment #4 from ferweer --- (In reply to wolthera from comment #1) > There's no screenshot attached? Sorry for late paste screenshot. (In reply to Boudewijn Rempt from comment #3) > Ah, that was fixed since. Best update your appimage. Oh sorry. Ok i update now. thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 --- Comment #2 from ferweer --- (In reply to wolthera from comment #1) > What make and model of monitor do you have? Sorry, I don't know you say what means. Maybe you say this case with monitor? I don't think so. But i use monitor. This > philips phl 246e7 I use settings brightness very low 0, contrust 3, and sharpnes 50 = So defaults. And yes im in to no radient room. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424574] New: eye paind and damage with colorize mask tool. change background color to gray?
https://bugs.kde.org/show_bug.cgi?id=424574 Bug ID: 424574 Summary: eye paind and damage with colorize mask tool. change background color to gray? Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY hi, sorry strange english. i use krita colorize mask tools. it easy and quickly. but that is have probrem. so eyed pain. from dark theme. what issue? i use dark theme. krita have dark theme. that is eye gentle and no eye damage for artist eyes. it's so good. by the way, i use colorize mask tools. colorize is use background with auto fill color is #FF. so it's can critical attack for eye. do you think? can krita change for #FF > transpalent or gray or hide? i feel that #FF is for many easy make for eye damage. however. other people can say. it's easy view for fill and no fill. yea, but i think that can it is other color. by the way. many web site many use #FF. i don't know for why use #FF. i see paper is not #FF. it's many difference color with ambient light. gray, cream, or calm orange, etc. just not #FF, this matter for many lamp room? eye and of course other body portion. that is important. you can have kind gentle thinking for your body. and for other. STEPS TO REPRODUCE 1. use colorize mask tools 2. you can see background auto fill #FF 3. you can say aa! eye pain! ..or you can have dameged eye to before sleeping. OBSERVED RESULT not use #FF EXPECTED RESULT colorize mask no autofill with #FF or colorize mask can have transpalent background or colorize mask can have to other no eye damage color with background. Krita Version: 4.3.1-alpha (git 741ba2a) Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-42-lowlatency Pretty Productname: Ubuntu 20.04 LTS Product Type: ubuntu Product Version: 20.04 Desktop: KDE -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424570] scroll bar issue on work space save window.
https://bugs.kde.org/show_bug.cgi?id=424570 --- Comment #2 from ferweer --- Created attachment 130336 --> https://bugs.kde.org/attachment.cgi?id=130336=edit workspace many have space -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424570] New: scroll bar issue on work space save window.
https://bugs.kde.org/show_bug.cgi?id=424570 Bug ID: 424570 Summary: scroll bar issue on work space save window. Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY hi. sorry strange english. but i discover this issue. krita have window for workspase layout save. this so awesame. bery usefull. but this window have issue for scroll bar view. you can see issue on screenshots. see? this not minimal text. i think that space is thumbnail position? but i can't see thumbnail. STEPS TO REPRODUCE 1. open layout save with workspace window. just it. 2. setting > configure toolbar > workspace OBSERVED RESULT workspace window and name have many many space. what this? EXPECTED RESULT list only for text. that is compact and easy lead and view and select. Krita Version: 4.3.1-alpha (git 741ba2a) Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-42-lowlatency Pretty Productname: Ubuntu 20.04 LTS Product Type: ubuntu Product Version: 20.04 Desktop: KDE -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423960] New: kdenlive if missing file path, can search but didn't replace missing file path.
https://bugs.kde.org/show_bug.cgi?id=423960 Bug ID: 423960 Summary: kdenlive if missing file path, can search but didn't replace missing file path. Product: kdenlive Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. add some file for kdenlive project, in some track. example jpg, mkv, 2. save project and close kdenlive. 3. change sources path for add file. 4. project open. kdenlive confirm missing file. you can tell for new file path for kdenlive. 5. project open, you can see missing file on track with new file path. OBSERVED RESULT but, you close again. and open again. kdenlive confirm again and again for you. this project use file is missing path. where file path? EXPECTED RESULT kdenlive is can do search and replace. for missing file path to new file path. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-40-lowlatency kdenlive-20.07.70-075dc41-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423469] New: suggest. kate can change and use background use image. on option.
https://bugs.kde.org/show_bug.cgi?id=423469 Bug ID: 423469 Summary: suggest. kate can change and use background use image. on option. Product: kate Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- hi, sorry strange english. suggested. kate is no background. kate can change background for only 1 color. If kate is can use gradation color or wallpaper. that great and beautiful view for text editor option. if you think > why use wallpaper for text editor? or > i think it's difficult see text. but please stop negation, you can see. ATOM = text editor, but yes can many editing file. so that IDE. atom need install package for change background image. but can change. or you can see pycharm = python editor. yes python IDE. that have option for change wallcolor and wallpaper. you can see settings > appearance & Behavior > Appearance > UI Options > Background Image. you can change background use imade. and opacity. or you know focus editor? that have'nt many editting option. but you can change documents editor ui! so background image, image opacity, image blur for text edit frame. text color, text style, text line spacing.. that many option. it's a beautiful and can raise for motivation. yes, but i know this feeling > no! that idea it's difficult text edit!! so because i suggested option like. you can change use background image or plane color only. that is gently method. sorry i no commit patch. i don't know programing for C## and QT. i can only tell for this idea. i try build kate on kubuntu 18.04, 19.04, but all faild. i don't know why dosen't build kate. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423467] New: dolphin is difficult grasp to many open tab.
https://bugs.kde.org/show_bug.cgi?id=423467 Bug ID: 423467 Summary: dolphin is difficult grasp to many open tab. Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- hi, sorry strange english. suggested. dolphin is difficult grasp to many open tab. because that open tab all wide 1 column. like libre office calc style. side to side. you can push <> change open tab. but..that is need action. so 1 push, you can change open neighbor tab. if you many open tab. example 20, yes it's many many open. but please try this. you may think that. hey, i tired to push <>. 1. all open but side full. tab view row change. exsample. exsample ABCDEFGH = open tab title. A|B|C|D|E|F|G|... A|B|C|D| = 1row E|F|G|H|...= 2row yes that probrem. dolphin have many height on tab list. but that is a clearlty view to all tab. 2. panel change. like kate text editor documents tree view. if you don't know that kate text editor documents tree view. kate > settings > Application > plugins > Document Tree View check on. that it. you can see all open document list on kate side bar on documents tab. exsample. exsample ABCDEFGH = open tab title. A| main folder or file view | B| main folder or file view | C| main folder or file view | D| main folder or file view | E| main folder or file view | F| main folder or file view | G| main folder or file view | ok that probrem. dolphin have many side width. but if you use sidebar infobar, or places. this can dock panel for other panel. sorry i no commit patch. i don't know programing for C## and QT. i can only tell for this idea. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417052] The default size of the window to be opened when opening a file in window mode is too small.
https://bugs.kde.org/show_bug.cgi?id=417052 --- Comment #2 from ferweer --- (In reply to Tymond from comment #1) > It is a bit small, but on the other hand, if it's too big to fit on the > screen, it would be difficult to make it smaller... and with fullHD devices > with 150% UI scaling, and the new Android tablets, it might be better to > leave it as it is. > > > I wish this information could be easily copied by pressing a button or > > something. > > Go to Help -> Show system information for bug reports. hi. just bit? im don't think so. umm but maybe, im think it is only im think. but therefore im suggested option for this method. 200px,500px,1024px,etc. yes you said right, now krita action 257-210px. for easy file use? only small devices and big display user. why option = that is krita can take free line of flow for extensive user. im think. and thanks! im don't knew before for this is option dialog! yes, im can easy copy for system infomation. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422505] dolphin preview info. does not recognize user theme. .txt .md etc
https://bugs.kde.org/show_bug.cgi?id=422505 --- Comment #1 from ferweer --- Created attachment 129088 --> https://bugs.kde.org/attachment.cgi?id=129088=edit dolphin attack to eye. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422505] New: dolphin preview info. does not recognize user theme. .txt .md etc
https://bugs.kde.org/show_bug.cgi?id=422505 Bug ID: 422505 Summary: dolphin preview info. does not recognize user theme. .txt .md etc Product: dolphin Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY sorry strange english. dolphin is have issue. i know this bug older bug report. but i cant found. maybe this bug or issue, developer said fix update is soon. that for 2020 june plans? sorry i dont have memorize. so, when this fix? if this bug report is duplicate. maybe that is so. sorry. STEPS TO REPRODUCE 1.dolphon > show panel > infomation OBSERVED RESULT if you used dark theme = eye gentle theme. dolphin gap generate and attack for your eyes. you have damaged eyes. EXPECTED RESULT user use gentle for eyes theme. dolphin recognize preview theme. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-33-lowlatency OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 419498] gwenview is can't load current directory with %U
https://bugs.kde.org/show_bug.cgi?id=419498 --- Comment #4 from ferweer --- (In reply to Nate Graham from comment #3) > That's not going to work. :) %U is a special symbol in .desktop files that > gets replaced with a space-separated list of URLs. For your purpose, you > need to pass the list of URLs yourself, or in the script. thanks. i changed script. gwenview ./* & -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 419498] gwenview is can't load current directory with %U
https://bugs.kde.org/show_bug.cgi?id=419498 --- Comment #2 from ferweer --- (In reply to Nate Graham from comment #1) > Are you actually running `gwenview %U`? Or giving it a real path, like > `gwenview /home/` ? thanks, i use shell script > .sh this sh in code hear #!/bin/bash gwenview %U& run this shell script example in ./documents you can get error. but can see file view. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 419523] New: kate can't showing on taskbar with open shell script
https://bugs.kde.org/show_bug.cgi?id=419523 Bug ID: 419523 Summary: kate can't showing on taskbar with open shell script Product: kate Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open kate with terminal command. but using shell script. example 2. kate -n path1/path2/name.txt& OBSERVED RESULT cant showing on taskbar. but can open name.txt. EXPECTED RESULT kate can showing on taskbar. from shell script. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-45-lowlatency -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 419498] New: gwenview is can't load current directory with %U
https://bugs.kde.org/show_bug.cgi?id=419498 Bug ID: 419498 Summary: gwenview is can't load current directory with %U Product: gwenview Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY hi, sorry strange english. %U command is open current directory to open path with application. but gwenview %U command on terminal get error. that is say Loading '%U' failed could not open file path. but strange action. gwenview is can open load directory. but first view say error. if i use cursor key action, can view file in current directory = open directory. why this is? why first view get error? STEPS TO REPRODUCE 1. some directory in open terminal 2. open terminal in some directory. 3. command. gwenview %U OBSERVED RESULT gwenview can open current directory. but gwenview first view get error. but you can view current directory file in gwenview with cursor action. EXPECTED RESULT gwenview need interaction %U. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-45-lowlatency ADDITIONAL INFORMATION maintenancer to busy? in opensources. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419286] please stop using tilde"~" on name.
https://bugs.kde.org/show_bug.cgi?id=419286 --- Comment #3 from ferweer --- (In reply to Tymond from comment #2) > If you're using Save Incremental backup, maybe you should use Save > Incremental Version instead. It saves 1.kra > 1_000.kra > 1_001.kra > > 1_002.kra, just as you wanted. The only difference is that it changes the > current filename of the file you're working on, so if you click plain "Save" > afterwards, it will save to the 1_00x.kra file, not to 1.kra. But it's easy > to get used to, it's actually a saving workflow I use and recommend. so i need changed method? umm. ok, i try. thanks you for suggest alternative method. and, zmv can't glub tilde. /~ \~ doesn't work =( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #6 from ferweer --- (In reply to Tymond from comment #5) > If you open a file that master Krita was supposed to save a layer style in > and you open it in Krita 4.2.9 (or earlier version), does it open the layer > style? or not? thanks, i glad reply. and i glad if this report became one improvement report for krita development i tested git db1cc49 again. yes, krita dosen't save kra on layerstyle. i discovery git db1cc49 generate .kra, too tiny file size. git 44d8e02 file save 1MB(example), git db1cc49, 55KB. and git 44d8e02, can't open generate layer style by git db1cc49. but can open file. can load except layer style only. maybe. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #4 from ferweer --- git 44d8e02 4.3.0prealpha can load layer style. i can't remember when download this version. git dac91df 4.2.9alpha can load layer style. git fc06350 #817 4.3.0prealpha CAN'T LOAD LAYER STYLE. all test environment with all krita config removed and clean. i test end. sorry for consecutive reported. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #3 from ferweer --- ok git 66b65ab can't. i think. i test other version? ok i download start for git fc06350 #817 this issue not happen on git dac91df. yes near 202502 version. an old. something wrong. what happen? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #1 from ferweer --- remove all configure > dose not work. .config/krita-scripterrc .config/kritadisplayrc .config/kritaarc .config/krita(DIR) i test 66b65ab. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 --- Comment #2 from ferweer --- sorry i mistake. i removed this directory. but dose not work. .local/share/krita(DIR) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419289] New: krita git db1cc49 was can't save using layer style.
https://bugs.kde.org/show_bug.cgi?id=419289 Bug ID: 419289 Summary: krita git db1cc49 was can't save using layer style. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY new file > any using layer style > save > open this saving file. you can't load layer style. empty layer. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-42-lowlatency OS Type: 64-bit git db1cc49 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419286] please stop using tilde"~" on name.
https://bugs.kde.org/show_bug.cgi?id=419286 --- Comment #1 from ferweer --- oh i mistake. sorry. krita rename on save incremental backup is tilde~000 on name before extension. but tilde using is difficult using on terminal command. so example 1.kra > 1~000.kra suggest 1.kra > 1-000.kra 1.kra > 1 000.kra 1.kra > 1_000.kra -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419286] New: please stop using tilde"~" on name.
https://bugs.kde.org/show_bug.cgi?id=419286 Bug ID: 419286 Summary: please stop using tilde"~" on name. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY Hi. sorry strange english. krita was using prefix tilde"~" on name to save incremental backup. but tilde"~" is tilde expansion. on bash, on unix terminal command. https://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06 2.6.1 Tilde Expansion what issue? can't catch this tilde on zmv or mv or cp or find command. and using tilde"~"000 is name. expansion after. this difficultest change to terminal rename or cp or remove or search. i suggest. name.extension > name-000.extension or name 000.extension (using space) any using except tilde"~" name. and name change. what think this? Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-42-lowlatency OS Type: 64-bit git db1cc49 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418561] menubar show No text.
https://bugs.kde.org/show_bug.cgi?id=418561 --- Comment #1 from ferweer --- Created attachment 126640 --> https://bugs.kde.org/attachment.cgi?id=126640=edit no text on menu bar -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 418561] New: menubar show No text.
https://bugs.kde.org/show_bug.cgi?id=418561 Bug ID: 418561 Summary: menubar show No text. Product: gwenview Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY gwenview menu bar > No text but can select menu item. and action is no problem. only issue is menu bar category name. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 417830] New: if using graphic tablet stylus on gwenview is can't move on image window with zoom or 100%
https://bugs.kde.org/show_bug.cgi?id=417830 Bug ID: 417830 Summary: if using graphic tablet stylus on gwenview is can't move on image window with zoom or 100% Product: gwenview Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY using graphic tablet stylus doesn't move on image window. only can with mouse. kde is have this issue other application too. kdenlive, and taskbar folder view. https://bugs.kde.org/show_bug.cgi?id=416421 but a case resolved for desktop effects window scroll bar. systemsettings5. so i think this issue is can solved too. this issue open from qt5.12.4. fix plan is qt version 5.14.1 later. https://github.com/linuxwacom/xf86-input-wacom/issues/93 https://bugreports.qt.io/browse/QTBUG-77826 Likely to be a workaround? write this code for .profile. “QT_XCB_TABLET_LEGACY_COORDINATES=1” or “export QT_XCB_TABLET_LEGACY_COORDINATES=1” but, doesn't this method cannot fix this issue for ubuntu user. why? i don't know. some difference opensuse or arch and ubuntu, maybe. opensuse tumbleweed use qt 5.14.1. but have this issue yet. so The cause of the problem is qt application side? STEPS TO REPRODUCE 1.using graphic tablet stylus 2. image open 3. zoom or 100% 4. click and move stylus. OBSERVED RESULT if using graphic tablet stylus on gwenview is can't move on image window with zoom or 100% EXPECTED RESULT can move with graphic tablet stylus on image window. SOFTWARE/OS VERSIONS graphic tablet: wacom tablet bt M Operating System: openSUSE Tumbleweed 20200214 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-1-default OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416421] Effect list scroll bar rejects operation with graphic tablet stylus
https://bugs.kde.org/show_bug.cgi?id=416421 --- Comment #3 from ferweer --- sorry this video too small. where can attachment 2 minute video file on web site? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416421] Effect list scroll bar rejects operation with graphic tablet stylus
https://bugs.kde.org/show_bug.cgi?id=416421 --- Comment #2 from ferweer --- Created attachment 126079 --> https://bugs.kde.org/attachment.cgi?id=126079=edit cant scroll on effect list and other menu window. cant scroll on effect list and other menu window. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416421] Effect list scroll bar rejects operation with graphic tablet stylus
https://bugs.kde.org/show_bug.cgi?id=416421 --- Comment #1 from ferweer --- i created cant scroll movie. version 18 and newer. see? kdenlive can't scroll with graphic stylus. this bug confirmed from opensuse tumbleweed so qt 15.14.1. and kubuntu 19.10. qt cant fix this bug? https://bugreports.qt.io/browse/QTBUG-77826 or maybe this issue with kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #11 from ferweer --- Oh, I made a mistake. The version of kubuntu that confirmed that no issues were addressed in today's installation was 19.10! If this became a major problem, the development team might have been willing to deal with it, right? Nobody writes here, it's stupid, and reporting bugs seems useless. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #10 from ferweer --- Well, frankly, I'm very disappointed. Today's installation confirms that neither kdeneon nor kubuntu19.04 addresses this issue at all. Users who do some activities on the pc using graphic tablets may want to use another distro or windows instead of kdeneon. Is kdeneon for light users who only use the pc for light internet and video playback? And ubuntu has no control over this. Because of qt? And kdeplasma can not cope? How do you deal with the current development of kdeneon, what about it? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #9 from ferweer --- When I tried installing neon, it was qt5.13.2 today. Since this was done in a virtual box, it is not suitable for checking the operation of the tablet stylus, but considering that the update of qt5.14 has not hit, it may not have been improved yet.I'm worried about making my system kubuntu19.10. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #8 from ferweer --- A related report was also on the forum, but no one is currently speaking. https://forum.kde.org/viewtopic.php?f=17=162089=wacom QT_XCB_TABLET_LEGACY_COORDINATES=1 By the way, this solution does not help anything in ubuntu. The effect window and gwenview of kdenlive are software that cannot be operated with a tablet stylus even with 19.04. There was no change even if I tried this workaround. sad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417052] New: The default size of the window to be opened when opening a file in window mode is too small.
https://bugs.kde.org/show_bug.cgi?id=417052 Bug ID: 417052 Summary: The default size of the window to be opened when opening a file in window mode is too small. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY Set to open krita document in sub window. 1. Settings> general> multiple> subwindow Now when you open kra with drag and drop, it will open in a window and you can stack and sort. OBSERVED RESULT But this default is too small. When measured, there is only about 257-210? Certainly a small window may be easier to handle on a laptop etc., but is there any setting to make this larger? At present, resizing is very troublesome. EXPECTED RESULT Set default value to open window. If the user sets an arbitrary size, it may be better to set a default value and select it. In the example> 200px, 500px, 525px, 1024px, etc. specific size preset. Regardless of the image size, it will be displayed in the window size that matches the default value. If the opened image is smaller than the window size, it would be nice to be able to choose whether to fit it by enlarging it or display it at the center of the window with 100% display. Also, select the default value for the image magnification and open it. For example, if it is better to keep a small window, set the value to 15% of the image. A window is set and opened at 15% of each image size. However, this setting can be especially problematic when opening small images! At 15% of 100px it will be much more difficult to operate as a window. Therefore, I think it would be more convenient to set an arbitrary size so that the user can set it. krita git 5e5eb3b I wish this information could be easily copied by pressing a button or something. Like kubuntu or pcinfo. It takes time and effort to manually enter each time. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 if you want to know the reason for the "why 19.04 system?"> bugs.kde 416361 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 334847] When reaching the last image and trying to view next, an unergonomic menu is shown
https://bugs.kde.org/show_bug.cgi?id=334847 --- Comment #17 from ferweer --- The problem is that you can't apply this fix except by applying a patch. Regular users will not post bugs to the bug tracker. Also, even if you can post it, you may not know how to apply the patch. Then, this is just a recognition that ordinary users are just Image viewer that keep displaying difficult-to-use dialogs. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416818] Dolphin address paths cannot be manipulated on directories with long names on externally connected drives.
https://bugs.kde.org/show_bug.cgi?id=416818 ferweer changed: What|Removed |Added Resolution|INTENTIONAL |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from ferweer --- (In reply to Kai Uwe Broulik from comment #1) > It shortens the address bar to start from the closest places in your Places > panel. This is by design. > > You can change this in Configure Dolphin → Startup → Show full path inside > location bar. Apparently he does not read what he wrote. >From the closest location in the location panel? and what are you saying? mnt / mountdrive / dirA / longname In this case, longnamedir hides the top directory mnt / mountdrive / dirA /. This is the system directory. If it was ./home/directory/dirA/longname, it would be strange because ./home/directory/dirA/ would not be completely hidden. Do not resolve without reading and understanding. The description is completely off the mark. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416818] New: Dolphin address paths cannot be manipulated on directories with long names on externally connected drives.
https://bugs.kde.org/show_bug.cgi?id=416818 Bug ID: 416818 Summary: Dolphin address paths cannot be manipulated on directories with long names on externally connected drives. Product: dolphin Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY How about adjusting the display of the address bar? Currently, if you have a long name, you will not be able to operate the address bar first. STEPS TO REPRODUCE 1. dolohin>startup>checkon for show full path inside location bar 2. you move long name directory 3. you cant click top directory. OBSERVED RESULT exsample > ./home/user/directory This is the normal display. If the name of the directory is short, the operability that the top directory etc. can be clicked immediately is good. But what if this is a long name? exsample > ./home/user/directory/longnamedirectoy dolphin view only mounted external hdd drive >/longnamedirectoy All names of the top directory are omitted, making it impossible to click and move. Because only /longnamedirectoy is displayed. And this is weird. This only happens for mounted external hdds. In other words, this problem does not occur in the system directory. Why do dolphins behave differently in external hdd and system hdd? (same sata cable connection, not usb connection) dolphin view only system drive > ./ho/us/dir/longnamedire.. EXPECTED RESULT Make the same display and behavior as the system hdd display even if it is an external hdd. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416677] What is the meaning of the track line painted red when this track is added?
https://bugs.kde.org/show_bug.cgi?id=416677 --- Comment #7 from ferweer --- The check was done with kdenlive-20.03.70-0567093-x86_64.appimage. Hmm ... unfortunately this issue is still being displayed. When you add a track, a track painted red is added. The only thing that was not painted red is when adding an audio track, and the remaining video tracks and AV tracks are both red. And the audio record track is also red. Strangely, video tracks that turn red when adding tracks do not turn red. I do not understand the behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 --- Comment #7 from ferweer --- (In reply to Jean-Baptiste Mardelle from comment #5) The check was done with kdenlive-20.03.70-0567093-x86_64.appimage. The names have been properly reduced and the buttons in the effect state are now tighter and easier to operate, thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416680] Shortcut keys do not have :collapse: and :expand:
https://bugs.kde.org/show_bug.cgi?id=416680 --- Comment #4 from ferweer --- The check was done with kdenlive-20.03.70-0567093-x86_64.appimage. The effect selected in the effect list and the track selected in the track could be collapsed and expanded using shortcut keys. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416680] Shortcut keys do not have :collapse: and :expand:
https://bugs.kde.org/show_bug.cgi?id=416680 --- Comment #3 from ferweer --- you have to use a mouse to check each one.(In reply to Jean-Baptiste Mardelle from comment #1) OK, I checked both collupse / expand in the track and effect list. You're doing great things! Thank you! By the way, the annoyance is that the effects list doesn't work with a tablet stylus (this is reported in a separate bug for both kdenlive and xsetwacom), so -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #7 from ferweer --- add Added application that some screens cannot be operated with tablet stylus (maybe) kdenlive (stabel, appimage) https://bugs.kde.org/show_bug.cgi?id=416679 https://bugs.kde.org/show_bug.cgi?id=416421 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #6 from ferweer --- Information that it became qt5.14 could not be confirmed with the installation of neon just the other day. The qt version was still 5.12.4 in the system update. The confirmation was done on virtualbox and the neon iso used was neon-user-20200123-1116. Well, it is a wonder if this is updated in qt on kubuntu 19.10. Well, it is whether this is updated with qt of kubuntu19.10. If not, the next issue may be reported again. Of course, by the user operating the tablet stylus. > A / B / C / D or some apps cannot be operated with tablet stylus! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416690] New: Why move to deleted folder? on mount directory.
https://bugs.kde.org/show_bug.cgi?id=416690 Bug ID: 416690 Summary: Why move to deleted folder? on mount directory. Product: dolphin Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY By the way, there is a movement that prevents file operations such as moving to the deleted directory with dolphin. Why is this? If you go to the deleted folder first, you will get a warning. the file or folder / path / (deleted) does not exist. yea, That's obvious when you operate it. Why make this move? Press Delete, then go to that directory and what will it be? Warning? Confirmation? And this is a movement that only takes place on the mounted drive. I tried to reproduce it on the system drive, but I did not reproduce it. After several checks, I was able to confirm that this only happened on the mounted external drive! STEPS TO REPRODUCE 1. Mount and move external drive to create temporary directory 2. Press delete key to delete 3. dolphin moves with a warning, to the path where the deleted directory should have been. OBSERVED RESULT Dolphin going to the path where the deleted directory was, yes, there are no directories. Dolphin warns and says that this is a deleted directory. .. I know EXPECTED RESULT Do not go to the deleted path. This is not at all comfortable. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416681] There is no saving effect as a group, like the commentary page.
https://bugs.kde.org/show_bug.cgi?id=416681 --- Comment #1 from ferweer --- https://userbase.kde.org/Kdenlive/Manual/Effects -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416681] New: There is no saving effect as a group, like the commentary page.
https://bugs.kde.org/show_bug.cgi?id=416681 Bug ID: 416681 Summary: There is no saving effect as a group, like the commentary page. Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY It states that you can create groups and save effects, but as you know this does not apply to the current kdenlive. Only save effect and create region are here for some reason. So how to save as an effect group in the current kdenlive? I do not know. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 kdenlive appimage 20.3.7 and 19.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416680] New: Shortcut keys do not have :collapse: and :expand:
https://bugs.kde.org/show_bug.cgi?id=416680 Bug ID: 416680 Summary: Shortcut keys do not have :collapse: and :expand: Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY It's good to have smaller effects and tracks to increase editing comfort. But I wish I could assign a shortcut key to it. OBSERVED RESULT At the moment you can only :collapse: and :expand: effect lists and tracks with a click EXPECTED RESULT Collapse effect property Expand effect property Collapse truck Expand truck It is better to have these shortcut key settings. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416679] New: In the appimage version, the effect property cannot be clicked with the graphics stylus.
https://bugs.kde.org/show_bug.cgi?id=416679 Bug ID: 416679 Summary: In the appimage version, the effect property cannot be clicked with the graphics stylus. Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY This could be due to a bug in qt. https://bugs.kde.org/show_bug.cgi?id=416361 But it might be a bug in kdenlive, I don't know. https://bugs.kde.org/show_bug.cgi?id=416421 I have posted a similar issue, Effect list scroll bar rejects operation with graphic tablet stylus. In addition to the scroll bar, the appimage version of kdenlive does not allow you to manipulate the property part of the effect tab. Drag and adjust values, insert keyframes, move, change the state of effects, etc. It seems that qt is involved, so it may be different again with updated kde plasma or kubuntu, neon. The bug fix for qt5.12lts is scheduled for January 30th, and neon seems to have been done just the other day, but it will take some time to reinstall the system to confirm it. OBSERVED RESULT It is difficult for users who use screen operations with the stylus of the graphics tablet to use appimage. It seems that the offset position of the graphics tablet is involved, but I'm not sure. EXPECTED RESULT It is necessary to be able to operate kdenlive with the stylus of the graphics tablet. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 test apimage:19.12.1 20.03.7 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416677] What is the meaning of the track line painted red when this track is added?
https://bugs.kde.org/show_bug.cgi?id=416677 --- Comment #3 from ferweer --- And a red line will appear on the status bar. This does not disappear when you save the file. I'm sorry I overlooked it, but it seemed to show something, but as far as I looked, I couldn't find any explanation for this. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416677] What is the meaning of the track line painted red when this track is added?
https://bugs.kde.org/show_bug.cgi?id=416677 --- Comment #2 from ferweer --- Created attachment 125357 --> https://bugs.kde.org/attachment.cgi?id=125357=edit after on save and restart kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416677] What is the meaning of the track line painted red when this track is added?
https://bugs.kde.org/show_bug.cgi?id=416677 --- Comment #1 from ferweer --- Created attachment 125356 --> https://bugs.kde.org/attachment.cgi?id=125356=edit emergency track red、 emergency track red. sorry i be joke for description title. but i think this happen is like emergency. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416677] New: What is the meaning of the track line painted red when this track is added?
https://bugs.kde.org/show_bug.cgi?id=416677 Bug ID: 416677 Summary: What is the meaning of the track line painted red when this track is added? Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY Well, this is what I posted on the forum and did not find a solution. https://forum.kde.org/viewtopic.php?f=265=164221=427293#p427293 As an overview, when you add a track, the audio, video, and av all added tracks are painted red. What does this mean? To indicate that it has been added? Strangely, this means that the track's red fill disappears when you save and reopen the file. I also tried the following types of kdenlive to see different fairness. But this is all happening. 19.12.1.appimage 19.12.1 kdenlive from os repository 20.3.70 (apparently nightly's latest status seems to be abnormal) STEPS TO REPRODUCE 1. addtrack OBSERVED RESULT track zone all red.(this emergency?) EXPECTED RESULT This red fill caused a gap with the color theme and severely attacked the eyes, so we recommend avoiding it. To indicate that a track has been added, add an underlined color to the track name, or display an icon Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 --- Comment #6 from ferweer --- (In reply to Jean-Baptiste Mardelle from comment #5) That's a great thing! Thank you. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #5 from ferweer --- (In reply to Christoph Feck from comment #4) Ok, I want to see what this problem will be like. It's a really serious problem when using tablets with kubuntu or qt software. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416441] Add window rule Default name order, application name> window rule?
https://bugs.kde.org/show_bug.cgi?id=416441 --- Comment #5 from ferweer --- (In reply to Christoph Feck from comment #3) Thank you, I did not know Phabricator. I was worried about adding requests and suggestions there. (In reply to Christoph Feck from comment #4) I first came up with it. If users create requested and proposed tasks on the site used by kde developers, will it interfere with development? not? As you might expect, I am not a kde developer. I really agree with having separate tabs. for rules or name. It might be even better if it can be sorted. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 --- Comment #4 from ferweer --- (In reply to emohr from comment #3) thanks reply. But even appimage19.12.1 does not show scroll bar. I tried resetting local / share / kdenlive but it didn't help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416441] Add window rule Default name order, application name> window rule?
https://bugs.kde.org/show_bug.cgi?id=416441 --- Comment #1 from ferweer --- Created attachment 125236 --> https://bugs.kde.org/attachment.cgi?id=125236=edit Notation where similar names are arranged and it is difficult to read application rules Notation where similar names are arranged and it is difficult to read application rules -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416441] New: Add window rule Default name order, application name> window rule?
https://bugs.kde.org/show_bug.cgi?id=416441 Bug ID: 416441 Summary: Add window rule Default name order, application name> window rule? Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY window settings for application name This is the default, which will result in similar names appearing in the name list after adding many. ISimilar to another suggestion, https://bugs.kde.org/show_bug.cgi?id=416440, this is a suggestion to enhance the convenience of this window rule tab. How is it? STEPS TO REPRODUCE 1. systemsettings5>windows rules >windows rules OBSERVED RESULT App names follow similar naming conventions, making it difficult to identify which application is which EXPECTED RESULT Set the application name to the first display name, such as application name ー windows settings Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416440] New: Adding a sorting to window rules makes it easier to manage many rules
https://bugs.kde.org/show_bug.cgi?id=416440 Bug ID: 416440 Summary: Adding a sorting to window rules makes it easier to manage many rules Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY Managing windows with a myriad of myriad window rules is great. However, this rule list can not be rearranged, and it can be exported only one by one, so it is rather poorly functional. How about adding sorting and bulk export? STEPS TO REPRODUCE 1. systemsettings5 > windows management >window rules OBSERVED RESULT Many added (more than 10) rules cannot be sorted and can only be exported one by one EXPECTED RESULT Sorting may be most intuitive by name. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416421] New: Effect list scroll bar rejects operation with graphic tablet stylus
https://bugs.kde.org/show_bug.cgi?id=416421 Bug ID: 416421 Summary: Effect list scroll bar rejects operation with graphic tablet stylus Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY This could be due to a bug in qt. https://bugs.kde.org/show_bug.cgi?id=416361 But it might be a bug in kdenlive, I don't know. The scroll bar next to the effect list is not affected by any operations on the graphic tablet. The only way to operate here is to move with the cursor keys. For some reason (cooperation with related image processing software, convenience, coping with tenosynovitis, etc.), a user who is operating using a graphic tablet, that is, an operation that imposes inconvenience to a user who does not use a mouse. STEPS TO REPRODUCE 1. Using a graphic tablet 2. Click the scroll bar next to the effect list to operate OBSERVED RESULT Well, scrollbar doesn't respond EXPECTED RESULT Scroll bar can be operated on graphic tablet Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 --- Comment #2 from ferweer --- Created attachment 125222 --> https://bugs.kde.org/attachment.cgi?id=125222=edit The only way to show it is to widen the window -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 --- Comment #1 from ferweer --- Created attachment 125221 --> https://bugs.kde.org/attachment.cgi?id=125221=edit Hidden state icon -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416420] New: Effects with long names will not be able to click the status icon unless you adjust the window size.
https://bugs.kde.org/show_bug.cgi?id=416420 Bug ID: 416420 Summary: Effects with long names will not be able to click the status icon unless you adjust the window size. Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY An example is Chroma Key: Advanced (colorselection). You can check it in the screenshot. This completely hides the icons for the state manipulation of the effects (display state, reset items, delete, move order). Also, the only way to display the status icons is to increase the window size, there is no scroll bar! This will continue to cause this inconvenience unless the user adjusts the size of the property window. It is not convenient to operate only in such a long window. STEPS TO REPRODUCE 1. Display the effect list 2. Add Chroma Key Advanced 3. Keep the properity tab narrow. OBSERVED RESULT The status icon is pushed after the long name, making it difficult to operate and less convenient. EXPECTED RESULT Abbreviate appropriately and do not make the width too wide to display the name. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416418] New: The effect selection list can only be operated with the cursor and cannot be moved to the full top and last
https://bugs.kde.org/show_bug.cgi?id=416418 Bug ID: 416418 Summary: The effect selection list can only be operated with the cursor and cannot be moved to the full top and last Product: kdenlive Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY There is no choice but to move the select completely with the cursor key, not accepting the operation. Furthermore, in the effect list, it is impossible to move until the top and last are displayed with the cursor key. This is due to the inconsistency between the cursor movement and the effect list display, even though there are still items. STEPS TO REPRODUCE 1.Display the effect list 2. Operate the effect list only with the cursor keys 3. Try moving first and last. OBSERVED RESULT The last and top of the item cannot be displayed. EXPECTED RESULT Match the display position and the amount of cursor movement so that all items are displayed even with the cursor key movement operation SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #3 from ferweer --- befor > Is the fix for QTBUG-77826 supported? Fixed title. I thought I could prevent the same from being posted, but sorry if this wasn't the right fix -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 416361] When is the qt bug fix QTBUG-77826 where certain applications cannot be operated by wacomset added?
https://bugs.kde.org/show_bug.cgi?id=416361 ferweer changed: What|Removed |Added Summary|Is the fix for QTBUG-77826 |When is the qt bug fix |supported? |QTBUG-77826 where certain ||applications cannot be ||operated by wacomset added? -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 416361] Is the fix for QTBUG-77826 supported?
https://bugs.kde.org/show_bug.cgi?id=416361 --- Comment #2 from ferweer --- (In reply to Valerii Malov from comment #1) Thanks for the response. It seems that 19.04 users will not be able to update at least until the end of January, and it seems better for users using the kdeneon release to stop updating until it can be confirmed whether it was fixed on January 21. I will keep an eye on this bug fix. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 334847] When reaching the last image and trying to view next, an unergonomic menu is shown
https://bugs.kde.org/show_bug.cgi?id=334847 --- Comment #15 from ferweer --- I apologize for posting the duplicate first, sorry. Bug 416367 was added as a duplicate. This continues to happen on both Kubuntu 19.04 and 19.10, and it's surprising that this has happened for solong. I will commend those who are working on fixing this. I don't know why the fix https://phabricator.kde.org/D9039 for this is not yet added to gwenview. However, a bug ticket may occur until the option is added. I hope that the fix will be added quickly for those who do this. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416367] New: Reaching the end
https://bugs.kde.org/show_bug.cgi?id=416367 Bug ID: 416367 Summary: Reaching the end https://bugs.kde.org/attachment.cgi?id=125191=edit Dialog blocking view SUMMARY STEPS TO REPRODUCE 1. Open the directory with only one image. 2.Next, press to reach the end, show dialog to inform 3.This dialog will stay on for a few seconds and will interfere with your view. OBSERVED RESULT Also, it does not look good because it occurs repeatedly EXPECTED RESULT Add a config that does not display this dialog? It would be nice to be an option. Also, the location of the occurrence should be displayed not on the center of the view but on the status bar that is least obstructive. Even if you ask what to do with the user when it reaches the end, the convenience of this function itself is not much felt. In other words, it hinders the view and makes it hard to see the image! SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-38-lowlatency -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 416361] New: Is the fix for QTBUG-77826 supported?
https://bugs.kde.org/show_bug.cgi?id=416361 Bug ID: 416361 Summary: Is the fix for QTBUG-77826 supported? Product: wacomtablet Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY https://bugreports.qt.io/browse/QTBUG-77826 https://github.com/linuxwacom/xf86-input-wacom/issues/93 This is a qt based problem. This bug affects 19.10kubuntu and the rolling release of neon. To briefly explain the bug, certain applications can not be operated at all (tablet stylus operation only) because the tablet point coordinate position offset is shifted. The bug reported by the wacomtablet git team in response to this has been addressed promptly, and it seems that it will be addressed in qt 5.14, 5.15. However, until kubuntu and kde desktops incorporate this fix, 19.04 users and 18.04lts users will not be able to update due to applications that cannot be operated with a tablet stylus. Tablet styli are sometimes used not only for drawing but also as a replacement for mice (often as a treatment for tendonitis). So when will xsetwacom address this bug? On kubuntu19.10 I tried to install the day before yesterday, qt was still in the bugged version of 5.12.4. Examples of related applications Media player \ smplayer and vlc Screencast \ obs Media Viewer \ gwenview Virtual pc \ virtualbox Office \ libreoffice SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Should this be posted on the kde forum https://forum.kde.org/index.php if this is not the place to ask a question? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416238] kra file with Color profile betargb embedded is displayed in srgb.
https://bugs.kde.org/show_bug.cgi?id=416238 --- Comment #1 from ferweer --- Created attachment 125112 --> https://bugs.kde.org/attachment.cgi?id=125112=edit krita color space settings -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416238] New: kra file with Color profile betargb embedded is displayed in srgb.
https://bugs.kde.org/show_bug.cgi?id=416238 Bug ID: 416238 Summary: kra file with Color profile betargb embedded is displayed in srgb. Product: gwenview Version: 19.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- SUMMARY This is a krita file created using Color profile betargb. STEPS TO REPRODUCE 1. In krita, set as follows. 2. Toolbar> Image> Properties> Image color space> Profile: Beta RGB OBSERVED RESULT gwenview can also display kra files, but its color space is displayed in sRGB. Curiously, the png file exported from krita is displayed in BetaRGB. EXPECTED RESULT Display kra file with embedded BetaRGB as BetaRGB color space SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415533] Dolphin doesn't load duplicate paths at startup
https://bugs.kde.org/show_bug.cgi?id=415533 --- Comment #4 from ferweer --- (In reply to Elvis Angelaccio from comment #3) > Not so easy. The logic in DolphinTabWidget changed a lot after commit > 27e3907a3daf9a63d05c00a0ff74. yes, thought, this is clearly a not ease of use phenomenon. I don't want this issue to be left alone. first aid=I use kubuntu until it is fixed? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415533] Dolphin doesn't load duplicate paths at startup
https://bugs.kde.org/show_bug.cgi?id=415533 --- Comment #2 from ferweer --- what. Hope it will be fixed quickly.(In reply to Nate Graham from comment #1) > Confirmed. I don't recall that this was a deliberate change. Probably > accidental. what. Hope it will be fixed quickly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415624] Thumbnails spoil appearance without following theme
https://bugs.kde.org/show_bug.cgi?id=415624 --- Comment #2 from ferweer --- https://forum.kde.org/viewtopic.php?f=223=163621 I tried posting to the forum but there was no response. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415624] Thumbnails spoil appearance without following theme
https://bugs.kde.org/show_bug.cgi?id=415624 --- Comment #1 from ferweer --- Created attachment 124749 --> https://bugs.kde.org/attachment.cgi?id=124749=edit gap thumbnail of dolphin preview info panel. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415624] New: Thumbnails spoil appearance without following theme
https://bugs.kde.org/show_bug.cgi?id=415624 Bug ID: 415624 Summary: Thumbnails spoil appearance without following theme Product: dolphin Version: 19.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The thumbnails displayed in the info panel are displayed with a dazzling contrast gap even when using the dark theme. This will severely create gaps with your surroundings, even if you choose an eye-friendly theme, and will make a terrible attack on your eyes STEPS TO REPRODUCE 1. Make dolphin a dark theme using breezedark. 2.Display info panel 3.Select ods (libreoffice_calc file), text file, qtr (qtracter file) OBSERVED RESULT There is a thumbnail with terrible contrast due to the gap with the surroundings. EXPECTED RESULT You need to follow the dark mode or overlay with the color of the user theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65 Qt Version: 5.13 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415533] New: Dolphin doesn't load duplicate paths at startup
https://bugs.kde.org/show_bug.cgi?id=415533 Bug ID: 415533 Summary: Dolphin doesn't load duplicate paths at startup Product: dolphin Version: 19.12.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Previously, kubuntu19.04 used kde backport ppa At that time dolphin was able to open multiple tabs at startup even with duplicate paths For example, $dolphin /home/user/music /home/user/documents /home/user/music /home/user/documents This was a command that could open two music and documents tabs. Now in .kdeneon. dolphin 19.12.0 only opens one music and documents tab combination with this command. I use dolohin in split view. Why did you prevent opening duplicate paths at startup? Would you reconsider that there is an advantage to having a template method that starts dolphin with the default set? I want to open dolphin with a fixed combination of tabs at startup. please Would you consider the benefits of opening duplicate paths. Or attach a command or option that makes this possible! STEPS TO REPRODUCE 1. $dolphin /home/user/music /home/user/documents /home/user/music /home/user/documents OBSERVED RESULT Dolphin doesn't load duplicate paths at startup EXPECTED RESULT Dolphin can load duplicate paths at startup like kubuntu version dolphin. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5,17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION again. please Would you consider the benefits of opening duplicate paths. Or attach a command or option that makes this possible. -- You are receiving this mail because: You are watching all bug changes.
