Bug 282855 - [Dialogs] Programmatically set name of non-existent folder to ResourceAndContainerGroup
Summary: [Dialogs] Programmatically set name of non-existent folder to ResourceAndCon...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 281718
  Show dependency tree
 
Reported: 2009-07-08 10:07 EDT by Tatiana Fesenko CLA
Modified: 2019-09-06 15:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tatiana Fesenko CLA 2009-07-08 10:07:00 EDT
Now the user can manually type a name of a folder that does not exist yet into 'containerNameField', and the folder will be created later. However, it's not possible to make it programmatically, because ResourceAndContainerGroup#setContainerFullPath(IPath) checks if container actually exists. 
Allow the use to programmatically set name of  non-existent folder to ResourceAndContainerGroup
Comment 1 Susan McCourt CLA 2009-07-08 14:46:31 EDT
marking "API" since it would change the documented behavior (though not necessarily the signature) of existing API.  We might need new API to control whether programmatic creation is allowed, for clients that rely on the old behavior.

It seems like a reasonable request (a patch would make this more likely to happen).
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:36:55 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.