Bug 102550 - gnome_date_edit show time flag set to FALSE does not work
gnome_date_edit show time flag set to FALSE does not work
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: libgnomeui (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
David Lawrence
: MoveUpstream, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-08-17 11:42 EDT by Need Real Name
Modified: 2007-04-18 12:56 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-09 13:29:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
C source code. Compile to see error (2.37 KB, text/plain)
2003-08-17 11:50 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2003-08-17 11:42:44 EDT
Description of problem: gnome_date_edit "show time" flag set to FALSE does not
work when code is compiled through makefile.
Show-time flag set to FALSE does work OK when generated through GLADE Build and
compiled in
the GLADE project src directory.  But, when exact same code is put into a
different directory and becomes part of another application with it's own
makefile, after compile the time field shill shows even if the show-time flag is
set to FALSE.


Version-Release number of selected component (if applicable): gnomeui 2


How reproducible: see attached code to reproduce


Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:
Comment 1 Need Real Name 2003-08-17 11:50:45 EDT
Created attachment 93691 [details]
C source code.  Compile to see error

Compile using gnome 2 libs,

gcc -Wall % `pkg-config --cflags gtk+-2.0 libgnomeui-2.0` `pkg-config --libs
gtk+-2.0 libgnomeui-2.0`
Comment 2 Ray Strode [halfline] 2005-09-09 13:29:06 EDT
Hi,

Red Hat Linux 8 is very old and we no longer support it.  I am going to close
this bug, but if you can reproduce your problem on a recent version of Fedora
Core or RHEL, feel free to reopen.

Note You need to log in before you can comment on or make changes to this bug.