www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Did dmd forget how to read?

reply Johnson Jones <JJ Dynomite.com> writes:
main.d(157): Error: no property 'SetCursor' for type 
'gdk.Window.Window', did you mean 'getCursor'?

um... anyone see bug? It's there, I promise.
Aug 05
next sibling parent reply Cym13 <cpicard openmailbox.org> writes:
On Saturday, 5 August 2017 at 23:54:45 UTC, Johnson Jones wrote:
 main.d(157): Error: no property 'SetCursor' for type 
 'gdk.Window.Window', did you mean 'getCursor'?

 um... anyone see bug? It's there, I promise.
"setCursor" exists, but "SetCursor" doesn't (or your "bug" depends on code that you wrote and didn't share). I believe as both "setCursor" and "getCursor" are one character away from "SetCursor" dmd took the first one in alphabetic order or something. No need to panic ;)
Aug 05
parent reply Johnson Jones <JJ Dynomite.com> writes:
On Sunday, 6 August 2017 at 00:22:45 UTC, Cym13 wrote:
 On Saturday, 5 August 2017 at 23:54:45 UTC, Johnson Jones wrote:
 main.d(157): Error: no property 'SetCursor' for type 
 'gdk.Window.Window', did you mean 'getCursor'?

 um... anyone see bug? It's there, I promise.
"setCursor" exists, but "SetCursor" doesn't (or your "bug" depends on code that you wrote and didn't share). I believe as both "setCursor" and "getCursor" are one character away from "SetCursor" dmd took the first one in alphabetic order or something. No need to panic ;)
No one is panicking, so you can stop panicking that you think they are panicking. The point is that setCursor is much closer to SetCursor than getCursor. It should prioritize case differences first. SETCURSOR should still match setcursor better than getcursor or getCURSOR or whatever. But I'll get you a ascii star for realizing the issue /\ < > \/
Aug 05
parent Cym13 <cpicard openmailbox.org> writes:
On Sunday, 6 August 2017 at 02:10:43 UTC, Johnson Jones wrote:
 On Sunday, 6 August 2017 at 00:22:45 UTC, Cym13 wrote:
 On Saturday, 5 August 2017 at 23:54:45 UTC, Johnson Jones 
 wrote:
 main.d(157): Error: no property 'SetCursor' for type 
 'gdk.Window.Window', did you mean 'getCursor'?

 um... anyone see bug? It's there, I promise.
"setCursor" exists, but "SetCursor" doesn't (or your "bug" depends on code that you wrote and didn't share). I believe as both "setCursor" and "getCursor" are one character away from "SetCursor" dmd took the first one in alphabetic order or something. No need to panic ;)
No one is panicking, so you can stop panicking that you think they are panicking. The point is that setCursor is much closer to SetCursor than getCursor. It should prioritize case differences first. SETCURSOR should still match setcursor better than getcursor or getCURSOR or whatever. But I'll get you a ascii star for realizing the issue /\ < > \/
If you feel that way you should post an issue on https://issues.dlang.org/ ; posting here is no solution. Or better propose an issue and a patch: I imagine that the code involved is fairly simple and unlikely to break anything so maybe it'll get merged quickly.
Aug 06
prev sibling parent Walter Bright <newshound2 digitalmars.com> writes:
On 8/5/2017 4:54 PM, Johnson Jones wrote:
 main.d(157): Error: no property 'SetCursor' for type 'gdk.Window.Window', did 
 you mean 'getCursor'?
 
 um... anyone see bug? It's there, I promise.
Please post bugs to bugzilla: https://issues.dlang.org/
Aug 06