I'm developping a remote control on iPhone for Mac OS and Windows. I use Bonjour framework and it's working well on Mac OS. I can see on my iPhone the different Mac devices which have my server.
I would like to do the same thing on Windows with language C or C#.
I haver wrote a piece of code it does'nt work : my iPhone does'nt see the service.
Here's a line of code that can be wrong I think :
if(DNSServiceRegister(&service, 0, 0, HostName, "_esiearemote._tcp.", "", NULL,htonl(PORT), 0, NULL, reg_reply, NULL)!=kDNSServiceErr_NoError)
Have you got an idea ?
Thanks a lot !
Are you compiling it against dnssd.dll?
Have you tried using C:\Windows\system32\dns-sd.exe instead? At least as a debugging tool?
Is mDNSResponder (the Bonjour Service) running? Many people disable it.
Also the problem could be between your PC and the iPhone, check if the service is advertised correctly on your PC, with Safari, the BonjourFoxy Firefox Extension or the Bonjour SDK
I also posted a couple of links to Apple documentation (the dns-sd and dnssd.dll/dylib manpages) in another answer.
Related
I have written a JavaFX app running on Windows 10 machine in the office which has problems showing (painting/rendering) certain embedded controls such as a Pane with PdfBox when I connect to it with Remote Desktop for Mac. It shows only a black screen in the app instead of the pdf document.
When I connect using RDP from my Windows 10 machine at home to my Windows 10 machine at work, the app works just fine (the pdf is shown in the app).
I have the same problems using AnyDesk and Teamviewer.
The app only shows PDFs properly using a connection from Windows 10 to Windows 10 with Microsoft RDP.
It might be a JavaFX issue. Similar issues are described here (although not 100% identical):
https://bugs.openjdk.java.net/browse/JDK-8239589
https://bugs.openjdk.java.net/browse/JDK-8229394
However, since I guess Microsoft Remote Desktop for Mac is using the same technology as the Windows Desktop client, I would have expected it to work fine.
I have a Mac Mini M1 running the latest OS (Monterey) at the time of writing this post. I am also using the latest Remote Desktop client for Mac.
This problem is not new and was also present in older releases.
I have tried to play around with screen resolutions, both on Host and Client but nothing good came out of those tests.
Disabled also hardware acceleration in Remote Desktop for Mac preferences but it didn't change anything.
The machine at the office has the following specs (which I cannot change nor update)
Edizione Windows 10 Pro
Versione 20H2
Data installazione: 10/09/2021
Build sistema operativo 19042.1415
Esperienza Windows Feature Experience Pack 120.2212.3920.0
Anyone else who has seen this problem and perhaps resolved it?
Could it be a bug in either PdfBox or Remote Desktop for Mac?
Except for the above issue, the Remote Desktop Client for Mac is working great (not lagging as TeamViewer or AnyDesk) and the user experience is phenomenal.
PS: While this might be considered a programming question (since I wrote the app with JavaFX) but it might be better to post on another forum? If yes, which one? On the other hand, many similar posts (look at the suggested thread on the right) have been upvoted despite not dealing with programming issues.
Thanks.
How do you use PDFBox? I ask because this is not a JavaFX component. If you use a SwingNode for that it might be interesting to try one of my two PDFViewer demos here and see whether the problem persists.
https://github.com/mipastgt/JFXToolsAndDemos#awtimage
The difference is in how I do the rendering and maybe that makes a difference for your use-case too. But of course this is just a wild guess and I can't promise anything.
i am new to windows phone app development , i wanted to know
if is there any other alternative way to test a windows phone app apart from testing in a windows phone device and testing vs2012 built in emulator ???
1) The reason i have asked like these that i wanted to know if i can download a windows phone emulator separately and test my app in it.
2)Am i missing any other alternative provided ?
Please let me know.
Thanks in Advance.
No these are your options. You can start the emulator without VS, and you can deploy apps to it via a command line tool, but you don't get any of these without installing the WP SDK for VS2012. But since this is all free, is that a big deal?
You could submit your app to the store as a beta, and have invited users test your app on their phones.
This article may be of use, although it still requires .NET framework and some other dependencies (but I don't think you'll ever get away without using them):
http://www.codeproject.com/Articles/31861/Windows-Mobile-Development-Without-Visual-Studio
I am trying to write some android apps on Mac OSX and then test them on my Samsung Fascinate (Verizon), but ADB will not recognize the phone. I have tried everything from restarting adb, to reinstalling the SDK. It works on the linux/windows machine that I have, and I know Mac is recognizing the device, because it shows up in System Information.
Other people posted that EasyTether caused problems for them and I previously used EasyTether, but I removed every trace of EasyTether from my machine so that should not be the problem.
I also recently restored the phone to stock through Odin so the problem is definitely not on my phone. If anything, it is a Mac problem.
Anyone have any ideas why this isn't working? I appreciate the help.
I was having the same problem. What fixed it for me was going in to the USB connection option after it registers on the phone side and changing to USB Mass Storage mode. This was counter-intuitive since PC Mode is supposed to be for debugging, but on the Mac this caused the device to register with the adb server and I am able to debug my apps; it will not work for me when the connection is set to anything else.
Just had the same problem and removing EasyTether and then disconnecting/reconnecting solved the problem for me.
This site has some tips (bottompart of the page) which could help you.
I have the tools installed for windows phone 7 development.
But, when I run the any of the sample apps I have to manually refresh my emulator's app window to see any changes.
Any ideas what I'm doing wrong? Or maybe a setting is wrong?
Thanks
I've got it on every machine I've tried- but they all have various Nvidia cards (desktop and mobile).
When I posted about this on the wp7 forums, they talked about wdm 1.1 (which I've got) and so far I have no fix.
My machines are all 64bit, so I'm wondering if this isn't some issue with them or the nvidia drivers- but I don't experience any other problems with the drivers outside of the emulator.
I think we're stuck for a while anyway...
I recently started creating applications for mobile devices and have successfully completed an application for the iPhone. I am now turning my attention to the Blackberry but haven't been able to find a convincing article or website that states that it can be done or a tutorial on how to do so. Can Blackberry apps be developed on Mac OS X? If yes, how do I go about doing so? Can anyone please point me in the right direction as I only have access to a Mac and really want to get this project on the road. Thanks in advance for your help.
UPDATE:
RIM has released a MacOS Eclipse plug-in for Blackberry Development: http://na.blackberry.com/eng/developers/javaappdev/macosx.jsp
While there is no built-in simulator, the plug-in DOES support USB tethered device debugging for the Torch 9800 handhelds. I plan to get one; they are ~$499 w/no contract. With a Torch and the new plug-in, Blackberry development is possible without using a VM. (Finally!)
PREVIOUS POST:
Building on MacOS works well once you set it up. I've had less luck with the simulator. On the whole though, being able to run Eclipse natively in MacOS and flip to a Windows VM only for debugging is a big win in my book.
You can get a MacOS version of preverify (see link below for details). I do my development with Eclipse on MacOS X and use Ant to build BB apps.
This blog is excellent and has many of the details to get you started:
http://www.azizuysal.com/2009/07/blackberry-development-on-mac-os-x.html (original link is dead. The "wayback machine" provides us with the original text content, but images and styling are lost to the sands of time. Still worth a read.)
The tricky part is getting the simulator to work. There is a Wine-based work-around, but on my computer, while the simulator was able to run under Wine, the LCD output was scrambled.
Currently, I build COD files from Mac, and my Ant build process drops them into a directory that is shared with a WinXP VM. I can run the simulator stand-alone in this VM. Debugging is also possible by installing Eclipse inside WinXP and pointing the debug configuration it at the source directories.
I've actually got a bit more magic. I enabled some of the Java 1.5 features by compiling against 1.5 and then translating the bytecode to 1.3 prior to the preverify script. (Blackberry only speaks a barbaric 1.3 java, flashback to circa 1992). It's not a silver bullet as some features still don't work, but it does cut down on the need to make everything an untyped Object reference.
Lately, I've been working on a x-platform framework to allow me to write app code once and build against both Android and Blackberry (both are Java). The Android part was easy. It's just a bitch to debug anything in Blackberry. Someone working at RIM decided that Blackberry didn't need to keep Exception stack traces unless there was a catch(Throwable), and then they could do something bizarre, non-standard, and undocumented (catching Throwable behaves weird). I've only kinda-sorta figured out a hack to get stack traces using JavaLoader.exe without breaking into the debugger, and it's barely worth it.
p.s., I now do x-platform development with a single code-base targeting Android, Blackberry, and Desktop. Desktop is great for testing app functionality, with very little Blackberry on-device testing needed once features work in the desktop 'simulator' (a Swing GUI built for debugging our games).
Even though certain components of the RIM development platform are java-based, such as the JDE - other components such as the preverifier and device simulators are implemented as native Windows executables.
Basically, the easiest way to do it is to install Windows on your Mac using Bootcamp or Parallels and run inside a real Windows environment on your Mac.
However, there are other "hackier" ways to do it using Wine, MacPorts, and a number of other tools - as an example see this blog post