Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
N
nx-libs
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
dimbor
nx-libs
Commits
4988e9bd
Commit
4988e9bd
authored
Mar 08, 2013
by
Alan Coopersmith
Committed by
Ulrich Sibiller
Oct 19, 2016
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix very weird indenting in nx-X11/lib/X11/GetFProp.c
Signed-off-by:
Alan Coopersmith
<
alan.coopersmith@oracle.com
>
Backported-to-NX-by:
Ulrich Sibiller
<
uli42@gmx.de
>
parent
001aeb55
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
12 deletions
+12
-12
GetFProp.c
nx-X11/lib/X11/GetFProp.c
+12
-12
No files found.
nx-X11/lib/X11/GetFProp.c
View file @
4988e9bd
...
...
@@ -29,24 +29,24 @@ in this Software without prior written authorization from The Open Group.
#endif
#include "Xlibint.h"
Bool
XGetFontProperty
(
Bool
XGetFontProperty
(
XFontStruct
*
fs
,
register
Atom
name
,
unsigned
long
*
valuePtr
)
{
/* XXX this is a simple linear search for now. If the
protocol is changed to sort the property list, this should
become a binary search. */
protocol is changed to sort the property list, this should
become a binary search. */
register
XFontProp
*
prop
=
fs
->
properties
;
register
XFontProp
*
last
=
prop
+
fs
->
n_properties
;
while
(
prop
!=
last
)
{
if
(
prop
->
name
==
name
)
{
*
valuePtr
=
prop
->
card32
;
return
(
1
);
}
prop
++
;
}
return
(
0
);
if
(
prop
->
name
==
name
)
{
*
valuePtr
=
prop
->
card32
;
return
(
1
);
}
prop
++
;
}
return
(
0
);
}
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment