| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #3261
| Application: | FLTK Library |
|---|
| Status: | 2 - Closed w/o Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | GLUT Emulation |
|---|
| Summary: | FLTK and glutChangeToMenuEntry |
|---|
| Version: | 1.3-current |
|---|
| Created By: | bsdooby |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | None |
|---|
| Fix Commit: | n/a |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | bsdooby
07:27 Oct 26, 2015 |
| There's a quirk in (FLTK's) glutChangeToMenuEntry() function:
it should be possible to dynamically change menu entries in glut's
context menu. In the current versions this is not possible as a
pointer gets copied which might point to an already invalidated
object. It would be a "better" approach to copy the string each time an update is done on the menu. | |
| |
| #2 | AlbrechtS
10:44 Apr 16, 2024 |
| I don't see anything wrong with the current implementation. FLTK stores the pointer to the given menu text (label) in the menu. Neither the documentation of
glutChangeToMenuEntry(): see https://linux.die.net/man/3/glutchangetomenuentry
nor
glutAddMenuEntry(): see https://linux.die.net/man/3/glutaddmenuentry
specify that the string should be copied.
Therefore I'm closing this STR now.
If I misunderstood the problem or if it still needs resolution, please discuss the issue in fltk.general before potentially opening a GitHub issue.
-> https://groups.google.com/g/fltkgeneral | |
[ Return to Bugs & Features ]
|
| |
