| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #3158
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 3 - Moderate, e.g. unable to compile the software |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | When creating a Fl_Double_Window and using the clear_border() function consumes a core |
|---|
| Version: | 1.3.3 |
|---|
| Created By: | pakulas |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | None |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | pakulas
19:37 Nov 20, 2014 |
| When I create a class from Fl_Double_Window for creating a child window and in my constructor, I am calling the clear_border() function, it seems to consume a core to 100% utilization.
class ChildWnd : public Fl_Double_Window {
public:
ChildWnd(int x, int y, int w, int h, const char *l) : Fl_Double_Window(x, y, w, h, l)
{
set_non_modal();
/*!911 - This seems to cause a CPU core to consume 100% */
clear_border();
/*!911 - This seems to cause a CPU core to consume 100% */
position(x, y);
label(0);
resizable(this);
end();
}
}; | |
| |
| #2 | pakulas
19:39 Nov 20, 2014 |
| Forgot to also add that this is happening on Windows 8.1 x64. | |
| |
| #3 | AlbrechtS
01:43 May 25, 2015 |
| Thanks for the report. However, I can't confirm this issue with current svn.
I used the attached file str-3158.cxx to test and everything worked well - no CPU loop issues. The program behaves well under Windows 8.1 64-bit.
Note that I compiled a 32-bit app using the mingw-w64 (32-bit) compiler:
i686-w64-mingw32-g++ --version
i686-w64-mingw32-g++ (GCC) 4.9.2
I could also try a 64-bit app, but before I do this, please answer the questions below.
Please tell us which compiler/build tools you used and whether you can reproduce the issue with the attached test file. If not, please post a short, but complete (compileable) test file like the one I posted.
Which source distribution did you use? The release tarball, a weekly snapshot, svn? Please try at least the latest weekly snapshot or current svn for further tests. TIA. | |
| |
| #4 | AlbrechtS
01:59 May 25, 2015 |
| After reading the OP a second time I'm wondering if you wanted to create
(1) a real child window (embedded in its parent window) or
(2) another independent (non-modal) window w/o borders
If it was (1) then set_non_modal() and clear_border() should not be used. These are methods used to setup real windows (2).
Anyway, attached file | |
| |
| #5 | AlbrechtS
02:02 May 25, 2015 |
| [continuing..]
Anyway, attached file str-3158_child.cxx shows case (1) w/o removing the above mentioned statements, and I still can't reproduce the issue. | |
| |
| #6 | AlbrechtS
11:17 Jul 17, 2015 |
| This STR has not been updated by the submitter for two or more weeks and has been closed as required by the FLTK Configuration Management Plan. If the issue still requires resolution, please re-submit a new STR.
If you still have the issue with FLTK 1.3.current-svn please drop a note in fltk.general referring to this STR so we can reopen it. Please do also post a full, compileable test program that shows the issue. | |
[ Return to Bugs & Features ]
|
| |
