Bug 75578 - Wish: Better not use modal window for "add method" "add class", "add attribute"
Summary: Wish: Better not use modal window for "add method" "add class", "add attribute"
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: language (show other bugs)
Version: 1.0.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2004-02-19 05:08 UTC by Xu Jian
Modified: 2018-10-21 04:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Xu Jian 2004-02-19 05:08:19 UTC
Version:           3.0.1 (using KDE 3.2.0, compiled sources)
Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
OS:          Linux (i686) release 2.4.23-workstation2

When adding new methods or attributes to class or, 
new class to the project. The wizard window is "modal"
so that when it is open, I can not access other parts,
e.g. the class view tree.

This is not good setting I think for usrs may need to 
reference (methods in base class). For me, I have to 
write the information down to a paper first, and then
go to the "add xyz" dialog.

And why there is nowhere to input documents for methods and attributes in the wizard dialog?

Thanks.
xujian@cse.unsw.edu.au
Comment 1 Amilcar do Carmo Lucas 2004-07-19 22:50:27 UTC
AFAIK this is fixed in HEAD.
Comment 2 Gaël de Chalendar (aka Kleag) 2005-06-25 09:58:37 UTC
Using a few weeks old CVS version on KDE 3.4.0, this is not fixed: The "New Class" dialog is still modal. 
So I can use it only for the class name...
Comment 3 Andreas Pakulat 2010-04-12 18:46:38 UTC
To clarify: If the class wizard would show you the list of member functions from the base class(es) having it modal would be ok right?
Comment 4 Xu Jian 2010-04-12 20:42:27 UTC
Giving more information may help but may still be insufficient. For example, I often need to "FIND" the base class and also explore the class inheritance diagram to make sure the new class is correctly designed.

 What is the design reason to make it a "modal" window?
Comment 5 Andreas Pakulat 2010-04-12 20:52:50 UTC
(In reply to comment #4)
> Giving more information may help but may still be insufficient. For example, I
> often need to "FIND" the base class and also explore the class inheritance
> diagram to make sure the new class is correctly designed.

But thats doable before even starting the wizard.

>  What is the design reason to make it a "modal" window?

Making it modal disallows the user to change stuff behind the wizards back. I don't know the implementation off-hand, but its a lot easier for it if it can fetch the data it needs once instead of having to poll for it. Apart from the fact that not everything in KDevelop sends out a notification if something changes.
Comment 6 Xu Jian 2010-04-12 21:28:21 UTC
That's what I have described in the original bug report. I need to write things down to a paper for what I need to input to the wizard, which is inconvenient.  And even I have a good memory and have planned before opening up the wizard, it often happens that I need to go back to the IDE for other information.
Comment 7 Andrew Crouthamel 2018-09-20 22:08:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-21 04:58:19 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!