Search found 153 matches
- Tue Jun 09, 2009 1:51 pm
- Forum: Platform Related Issues
- Topic: Bumping it... the iPhone?
- Replies: 4
- Views: 1513
Hi! I suppose the major problem in porting to iPhone might be, that AFAIK iPhone apps are written in objective C. I'm not really sure if much work has been done to port wxWidgets using objective C. Indeed they are written in Objective-C, but don't think that's a great problem, as mixing Objective-C...
- Tue Jun 09, 2009 2:27 am
- Forum: Platform Related Issues
- Topic: Bumping it... the iPhone?
- Replies: 4
- Views: 1513
Bumping it... the iPhone?
I'm sitting here at WWDC09 and am trying to learn everything there is about iPhone development. The iPhone truly appear to be a powerful platform, and covering it with wxWidgets would really be useful. :arrow: Anyone know the status of the port of wx to iPhone? With that I mean fresh information. Th...
- Tue Jan 13, 2009 10:15 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
Always welcome ;-) I had one question. Was this trouble (and its solution) relevent to wxWidgets 2.6.3 or you've encountered it in other versions too? My profile says I'm using 2.6.3 but that is for my main commercial projects. This project is personal (currently 8) ) and I thought it a good idea t...
- Mon Jan 12, 2009 8:05 pm
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
You know, I've just found one of my old wxWinCE test apps here and made a quick test that displays a message box with values got from wxDisplaySize()... It reports correct size for QVGA (240x320), VGA (480x640) and Square VGA (480x480) emulators and also on 480x800 device (some Toshiba, don't know ...
- Sun Jan 11, 2009 10:01 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
I'd like to point out, that knowing the screen size is not as important as blitting bitmaps correctly on screen. Every access to the screen maps one (software) pixel to 2x2 (hardware) pixels on screen, so everything gets large and blocky. I'm baffled by the behavior and I have only encountered this ...
- Sun Jan 11, 2009 9:52 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
It's not related to wxWidgets, it's compiler/SDK feature. Well, if you're using Visual Studio with appropriate SDK selected, it defines those for you. But I suggest you doublecheck your build command line to see what gets defined and if it's really appropriate for the platform you build for. Especi...
- Sun Jan 11, 2009 9:46 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
- Sun Jan 11, 2009 9:25 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
Follow-up: I'm not really sure about problem origin right now, need to get home and look into it in more detail, but this just came up in mind: Are you using correct preprocessor directives for your platform? I mean, __POCKETPC__, __SMARTPHONE__, __HANDHELDPC__, so on?.. I'm using the standard wxWi...
- Sat Jan 10, 2009 8:25 am
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
What code do you use to fetch screen dimensions? All of them, so to speak ;-) In wxWidgets I use wxSystemSettings::GetMetric(wxSYS_SCREEN_X) which is mapped to the Win32 call ::GetSystemMetrics . But even trying the Win32 call ::GetDeviceCaps yields an incorrect answer. I also tried the Win32 call ...
- Fri Jan 09, 2009 10:05 pm
- Forum: Platform Related Issues
- Topic: wxWinCE reports incorrect screensize...
- Replies: 16
- Views: 3817
wxWinCE reports incorrect screensize...
I'm playing around with my HTC Touch HD with a screensize of 480x800 pixels. It has Windows mobile 6.1. The SDK from Microsoft provide a close approximation of the device at the same screen resolution. Using wxWidgets 2.8.9 and wxWince I'm doing a trivial Hello World with the sole purpose of printin...
- Sat Nov 08, 2008 9:53 am
- Forum: Platform Related Issues
- Topic: How mayture is wxX11 ?
- Replies: 1
- Views: 1082
How mayture is wxX11 ?
I'm currently using wxGTK on Linux. Just for fun, I thought I would try wxX11 as an alternative. How mature is that port right now?
Will I be able to run an wxX11 app directly under Gnome?
Thanks!
Will I be able to run an wxX11 app directly under Gnome?
Thanks!
- Sat Oct 25, 2008 8:08 am
- Forum: Platform Related Issues
- Topic: wxGTK: Absurd wxWidgets version conflict
- Replies: 6
- Views: 1781
I am not sure what you mean. All you need to do is recompile with 2.8 whatever you compiled with 2.6. If you have ever used a Photoshop plug-in or a VST plug-in, the similarities are there. The host may choose to load or not load the plug-in. This is done using dlopen. In a host / plug-in environme...
- Fri Oct 24, 2008 8:56 pm
- Forum: Platform Related Issues
- Topic: wxGTK: Absurd wxWidgets version conflict
- Replies: 6
- Views: 1781
Hi, First and most obvious: why not upgrade 2.6.x to 2.8.x? I don't think that is obvious. One of the binaries is a plug-in to the other, and as soon as one of them is build by a another vendor, the problem becomes critical. Besides, it's a OS related problem I guess? Second, how did you compile 2....
- Mon Oct 13, 2008 1:05 pm
- Forum: Platform Related Issues
- Topic: wxGTK wxCriticalSection behaviour
- Replies: 0
- Views: 448
wxGTK wxCriticalSection behaviour
Hi,
Using wxGTK 2.6, are critical sections recursive? In other words, may a thread enter the section any number of times without deadlocking?
Thanks!
Using wxGTK 2.6, are critical sections recursive? In other words, may a thread enter the section any number of times without deadlocking?
Thanks!
- Mon Oct 13, 2008 8:39 am
- Forum: Platform Related Issues
- Topic: wxGTK: Absurd wxWidgets version conflict
- Replies: 6
- Views: 1781
wxGTK: Absurd wxWidgets version conflict
Hi, For certain reasons we have a project consisting of the following odd mix: * A wxGTK 2.8 based app using dynamically loaded wx-libraries. * A wxGTK 2.6.3 based shared library (*.so) with statically linked wx-libraries. The app loads the shared library using a standard mechanism. The problem occu...